It’s also already on the tower that it launches from, which drastically reduces the expense and complexity of setting it up for its next launch, making it easier and faster to reuse.
Isograph is very much a work in progress, and more of an experiment to the improve developer experience of building GraphQL-backed apps than a production-ready framework. The other frameworks are production-ready.
It has a lot of similarities to Relay under the hood. The primary difference is that in Relay, you import components, spread fragments and pass down fragment references to the only component that can read that fragment:
// in your GraphQL fragment:
user { ...UserName_user }
// and render it as
<UserNameRenderer user={data.user} />
Whereas in Isograph, you simply select the component and use it directly.
// in your isograph fragment
user { user_name_renderer_component }
// and, interpolate instead of using JSX syntax:
{data.user.user_name_renderer_component(additionalProps)}
Because the Isograph compiler knows that only the UserNameRenderer component will read that fragment, it can do all of the plumbing for you. Fragment refs, etc. don't exist.
There are potential, unimplemented performance advantages to this as well, such as defaulting to asynchronously loading the JS for UserNameRenderer if the fragment is deferred, instead of making that separate steps.
I am a web developer with years of experience transitioning to being a security researcher/engineer. I am currently studying penetration testing and reverse engineering binaries. Please no pure web dev job offers, I can easily find that kind of work! Right now I'm looking for my first job doing mostly security work.
I'm focusing on cybersecurity. Right now I'm doing the microcorruption.com CTF, just finished the stockfighter CTF. I read The Web Application Hacker's Handbook and am practicing pentesting the sample apps compiled by OWASP. [1] I want to learn to reverse engineer malware, and write cryptographically secure software like Tor.
I spoke to a guy who does pentesting and vuln finding for a living. He told me that if I'm interested in doing the same thing, I'd be better off doing a little reversing work and then going into open-source analysis as soon as possible. His reasoning is that, if you're doing this as a career, then you're working for companies who are asking you to audit them, and will almost always give you the source to work with.
You'd figure it out eventually, especially if it was exceedingly annoying and/or your job depended on it.
Example: what if your internet drops out for an hour every Sunday morning at 2am? You'd notice. (Mine does. Damn it Comcast!) If guy's wife relied on the printer similarly, it might be as acute as losing internet for you.
