DrFell

9 ms·

31.
by DrFell 5y ago
Because we're living now. It's our descendants who are screwed. Just don't have kids.
32.
by DrFell 5y ago
JavaScript is a great browser scripting language because it's the only browser scripting language. That's a whole realm of good times, and people can and should go nuts with it there. The problem started a decade or so ago with N
33.
by DrFell 5y ago
As an old webdev who was full-stack before Node even came out, and avoided it completely, all I can say is; Have fun, kids! jingle jingle
34.
by DrFell 6y ago
Most Node devs are JavaScript monoglots, who just recently learned frontend, and figure "Let's use JavaScript for everything!"
35.
by DrFell 6y ago
It's the extra layer of convolution. It's necessary in a browser, but when circled back to the server, it's vestigial. With Deno, you're using a classic OOP inspired superset of JavaScript, transpiling it to JavaScript,
36.
by DrFell 6y ago
I have a theory that TypeScript was not actually invented for frontend developers, it was created for non-frontend developers who were forced to deal with the frontend, and hated JavaScript. That's also why I think it's very funny
37.
by DrFell 6y ago
It's sad to see a serious thread about Node.js here, complete with mention of using TypeScript on the backend. Taps
38.
by DrFell 6y ago
The most complicated web development stuff is the easy technology taken to extreme levels of pseudo-sophistication. The technology that's unpopular because it's too complicated to learn is actually easier to build real projects wi
39.
by DrFell 6y ago
This will probably get worse as the value to engineers of fighting for architectural sanity diminishes in the modern semi-disposable project based job economy. I have no stake in the the companies future? OK, add another layer of abstracti
40.
by DrFell 6y ago
The amount of rookie webdevs who think contributing to an open-source project is a normal part of learning now is so baffling. How are you supposed to make significant contributions to any project worth a darn without any significant experi
41.
by DrFell 6y ago
I still think a plain old PHP site works just as well, and is easier and more flexible than any SSG system.
42.
by DrFell 6y ago
That's good, because I've been deliberately ignoring pop webdev technology in hopes this would happen.
43.
by DrFell 6y ago
The whole JavaScript SSR/SSG/hybrid app scene is changing too fast to be driven by anything more substantive than trendiness. Reminds me of dot com hysteria.
44.
by DrFell 6y ago
The comments here are mostly about framework clannism. Every framework has it's pros, cons, compromises, and quirks. I picked Angular because it was so advanced. I wanted the challenge, got to work on awesome teams, and learned so mu
45.
by DrFell 6y ago
Despite the literal phrasing, server-side rendering, as in SSRing a SPA, is not even close to what was happening in the 90's. That was much simpler, pure, and fun.
46.
by DrFell 6y ago
GraphQL is instant API to frontenders. Their justification for needing it is that the API team takes too long to implement changes, and endpoints never give them the data shape they need. The silent reason is that server-side code, database
47.
by DrFell 6y ago
I think at least part of the reason tech has become complex is because so many tech stacks today are a briar patch of 3rd party libraries and components that no one person can understand. The 'Don't reinvent the wheel' rule
48.
by DrFell 6y ago
How corrigible of them. We all know damn well they have no choice.
49.
by DrFell 6y ago
He didn't grind his own mirror, though. If you want to be a real ATM, you gotta make the mirror.
50.
by DrFell 6y ago
Using JavaScript outside a browser by running the V8 JavaScript browser engine on the server is a bit of a gimmick, but enough people can't bother to be a polyglot, and it's not that crazy. But, once you are writing code in TS, th
51.
by DrFell 6y ago
I am beginning to think the JavaScript ecosystem for non-browser environments is a deepening spiral. Learning another language does require effort, but the increasingly circuitous machinations being invented to continue using browser script
52.
by DrFell 6y ago
I thought the point of TypeScript was to transcend certain limitations of the JavaScript language, while still being able to write for browsers. It’s a bit awkward, you have a transpile the script, and generate source maps to debug it, but
53.
by DrFell 7y ago
My conjecture that consciousness is made of events is an attempt to explain why we see ‘the problem of time’. There are more widely accepted concepts around the subject, like the idea that all moments in time exists equally, not just now.
54.
by DrFell 7y ago
Clocks appear to tick because we are locked in a series of moments. The clock exists at all times it has or will show.
55.
by DrFell 7y ago
Causality, I guess would be my answer there.
56.
by DrFell 7y ago
The problem of time comes from the notion that we are matter existing through time, instead of realizing sentience is made of events.
57.
by DrFell 7y ago
Ah trends, the modern replacement for getting it.
58.
by DrFell 7y ago
I have been mutating data for decades without any unexpected behavior gremlins.
59.
by DrFell 7y ago
It is just as easy as lots of things we take for granted, line making a new app route, or component. That is a non issue.
60.
by DrFell 7y ago
If you're a backend dev that makes APIs, you probably won't like GraphQL (I am not one of those, BTW). If you have a big project with a team split into API devs and app devs, and you have to wait, then that is poor planing. Pl

More ›