jazzdan

6 ms·

1.
by jazzdan 5y ago
Yeah, exactly. Or even just not listed in `earthly ls`, maybe you'd still want to be able to call them manually for debugging purposes.
2.
by jazzdan 5y ago
+1 on `earthly ls`. I've also thought it would be valuable to have "public" and "private" targets. When looking at a new codebase it can be hard to know which targets I should use when developing, and which are pure
3.
by jazzdan 5y ago
As someone who worked on this it was exciting to get Replay working on three platforms (macOS, Linux, Windows), hopefully proving that our strategy[1] for recording and replaying programs works. [1] https://medium.com/replay
4.
by jazzdan 5y ago
(Replay engineer): Kind of! In the code viewer's left hand side gutter, the one that shows line numbers, if a line of code was never executed it is greyed out. Otherwise if you hover over it we show you how many times that code was exe
5.
by jazzdan 5y ago
(Replay engineer): Yes, replit has been working on adding similar functionality ( https://blog.replit.com/debuggest ). In fact: we've been collaborating with them on it! :)
6.
by jazzdan 5y ago
Self-hosted is on the roadmap, but getting this to be a universal technique is definitely going to be hard, no arguments there. Gotta start somewhere though!
7.
by jazzdan 5y ago
Replay deterministically replays the recording, so if the state of the application when you recorded it caused a network call, then when replaying it we will also "make" a network call _but_, instead of actually going out to the n
8.
by jazzdan 5y ago
(Replay engineer): Yes it does!
9.
by jazzdan 5y ago
(Replay engineer): In the long run we'd love for Replay to prove to the major runtimes that they should build support for this in to the runtime itself, rather than us maintaining many forks. The API that we designed for recording a ru
10.
by jazzdan 5y ago
(Replay engineer) Google is currently the only way unfortunately. We wanted to support secure logins at launch, with SSO and Multi-factor Authentication, and focus most of our efforts on the core product. As a result we just went with Googl
11.
by jazzdan 5y ago
(Replay engineer): we basically record all the inputs and outputs to a program. In the example of an HTTP request: when recording we'd record that a request was made, and the response. When replaying, rather than make the HTTP request,
12.
by jazzdan 5y ago
(Replay engineer): re: Windows, we have an alpha build out now, with a wider beta release coming later this year. re: on-prem, it's definitely something we plan to support, and something we have engineered in to the infrastructure. If
13.
by jazzdan 5y ago
(Replay engineer): We're big fans of RR and pernosco, I love to see those tools get their due. Replay is also designed to support backend programs. We [support Node]( https://github.com/RecordReplay/node ) today wit
14.
by jazzdan 5y ago
(Replay engineer): We support all the debugger features (breakpoints, step in to, step over) and more (step back). We emphasize console.log because we found that time traveling console.logs makes for a good demo, and engineers immediately g
15.
by jazzdan 5y ago
(Replay engineer): Hey davidten, thanks for trying Replay, sorry about the confusion. You definitely shouldn't need an invite. We're on it, getting a fix out now.
16.
by jazzdan 5y ago
(Replay engineer): That's something we'd love to enable in the future, but before we do we want to make sure that non-technical user can understand the implications of what they are sharing (a recording contains everything: every
17.
by jazzdan 5y ago
Replay employee here: We definitely want to enable something like that in the future. But first we need ensure the user's privacy is maintained. Right now a recording contains _everything_: all variables, all cookies, all network reque
18.
Solving the Laggy Human Shell Problem(blog.tilt.dev)
3 points by jazzdan 7y ago|0 comments
19.
Microservice Devs: Put Down the Particle Accelerator(blog.tilt.dev)
1 points by jazzdan 7y ago|0 comments
20.
Why Does Developing on Kubernetes Suck?(blog.tilt.dev)
5 points by jazzdan 7y ago|0 comments
21.
Observability Doesn’t Work in Dev(medium.com)
2 points by jazzdan 7y ago|1 comments
22.
Can Microservices Make Things Simpler?(medium.com)
1 points by jazzdan 8y ago|1 comments
23.
Comparing the PHP 7 and Hack Type Systems(dmiller.io)
46 points by jazzdan 11y ago|35 comments
24.
Experimenting with HHVM at Etsy(codeascraft.com)
150 points by jazzdan 11y ago|37 comments
25.
by jazzdan 12y ago
The HHVM team runs the tests of popular GitHub PHP repositories on HHVM, it's available here: http://hhvm.com/frameworks/ According to that 99% of magento2 tests are passing.
26.
by jazzdan 13y ago
Facebook's Hack lang is open source, though not publicly documented. This commit points out a lot of the implementation and test files: https://github.com/facebook/hhvm/commit/db9577b1409b74293fd9...
27.
ODA - Online Disassembler(onlinedisassembler.com)
50 points by jazzdan 14y ago|21 comments
28.
1975 Programming(varnish-cache.org)
1 points by jazzdan 14y ago|0 comments
29.
by jazzdan 14y ago
>No one’s going to give you a bonus for remembering the difference between inheritance and polymorphism: let’s face it, you’d take the 5 seconds to Google the definitions and move on. The point of those questions isn't to test whether y
30.
by jazzdan 14y ago
One good way to start building your security credentials is by becoming the go-to security guy on your team. Poke around the product you're working on and try to find security holes. Bring up security at code reviews. Besides just facilitat

More ›