shados

128 ms·

1171.
by shados 11y ago
For the people saying "go to HR", if I remember well from my friends who work there, Oracle's HR is something like 4 people for the entire company (everything is automated). So it's more like "send an email to HR pe
1172.
by shados 11y ago
You're totally right. I downloaded the latest release earlier and looked at the file size, and did it again right now, and you're correct. I still can't figure out where the hell I saw the smaller numbers earlier. I must have
1173.
by shados 11y ago
For React you kind of have to use the minified file size, because the dev file size is SHOCK FULL of dev-only validation and error messages and other logic that is made to be minified away. The prod build isn't even close to the same c
1174.
by shados 11y ago
point 1: merge smaller features more often. Multi-thousand line PRs suck no matter if they're squashed or not. point 2: As people mentioned, this is for PRs done by individual people, usually squashing their local history. If multiple
1175.
by shados 11y ago
Honestly, if I thought JSX was too complicated (it lints very well with ESlint, so even if it was problematic, you can just let the tool figure it out for you), all I'd do is use destructuring with the React.DOM built in element factor
1176.
by shados 11y ago
Flow's way of handling classes nominally and interfaces structurally is really nice. By the way, can you extrapolate on eslint and babel working to check symbols across modules? I don't think I ever noticed that feature.
1177.
by shados 11y ago
Redux is the only "new" thing in that list, and I could code it from scratch during a hackathon. It's also essentially a javascript port of what other framework and languages have been doing since before a lot of people readi
1178.
by shados 11y ago
Redux is 100~ lines of code without all the sanity check. Thunk is -4-. You kind of need to settle on some kind of design pattern on how your data exists, flows, etc. You'll want to be reasonably DRY doing it. Whatever you code will pr
1179.
by shados 11y ago
Until there's no 1:1 relationship between the client and the server APIs, or you don't control all parts of the server... Relay is amazing, but it makes assumptions about the server (its kind of the point).
1180.
by shados 11y ago
Generally when TypeScript is compared to C#/Java, it is about the syntax look, or when contrasting it to other type system such as, let say, Scala. And then it's very much on the C#/Java side of the fence. TypeScript definite
1181.
by shados 11y ago
The article mentions https://github.com/petehunt/react-howto . Its a damn good place to start.
1182.
by shados 11y ago
The reality is that these tools, eventually, are used by businesses trying to build stuff efficiently. If we were to have a hackathon, and I could use the stack I have at work (which contains some of these tools, plus our own secret sauce),
1183.
by shados 11y ago
What's the story for tooling though? I haven't looked at CSJS much, just the readme, but it seems like the CSS bit essentially is a string, so you don't get the same kind of tooling you can from either CSS files or javascript
1184.
by shados 11y ago
Bingo. And that, IMO, will be it. The problem right now is that people have no choice. They can use compiled to JavaScript languages, but they're ALL leaky abstractions. Once people can use the tool they want instead of the tool they h
1185.
by shados 11y ago
The ecosystem exploded because of a few core advances (ES6 finally coming out, Babel coming into light, the CommonJS approach to modules, the rebirth of functional programming on the frontend, etc). This is behind us now. If you sit in foru
1186.
by shados 11y ago
We had a discussion about this in my last team. It really comes down to the JS community being divided in 2. You have the first group, of which most of us were part of at least at some point: developing in our language of choice and being &
1187.
by shados 11y ago
Most people don't need these things. And more and more companies have devops and infrastructure teams that can deal with that. We're still in a world where every team is a snowflake (the closest things to breaching that was Rails
1188.
by shados 11y ago
ClojureScript is pretty fantastic, and Om had a lot of the ideas behind Redux before Redux (a bit like Elm). It's still a bit early to build a team revolving around FP though (it can be done, but you need a big company commitment in te
1189.
by shados 11y ago
Ramda really is awesome.
1190.
by shados 11y ago
If you want the React semantic without the size, you can just use something like https://github.com/developit/preact (which is like 3kb once deployed). You also don't need JSX if you don't want to. Using Reac
1191.
by shados 11y ago
eslint also has auto-fix support to some extent. I don't know how far JSCS pushes it though. The biggest thing is that whenever something new pops up, you can get an eslint plugin to lint it (eg: it took a wh ile for jshint to be able
1192.
by shados 11y ago
Don't be bummed :) The point was that there's no "obvious" solution. Something released in January needs a bit more time to become an obvious go-to. Doesn't mean it's not great or that it won't.
1193.
by shados 11y ago
It happens all the time because most UMD implementations are broken and make incorrect assumptions, so you often have to follow the "Fix broken modules" steps on https://webpack.github.io/docs/shimming-modules