HNHacker News
TopNewBestAskShowJobs

DrFell

108 karma · joined September 21, 2016

submissionscomments
DrFell··on Canada weather: Dozens dead as heatwave shatters records
Because we're living now. It's our descendants who are screwed. Just don't have kids.
DrFell··on Modern Javascript: Everything you missed over the last 10 years (2020)
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 Node. Too many people only learn JavaScript, become psychologically dependent on it, and they all collectively took it too far outside of a browser.

ECMAScript is a general purpose standard, but it was invented retroactively. Node is not ECMAScript in a server-side ECMAScript engine, it's JavaScript in a browser JavaScript engine. That's just too much of a force fit, and has wasted too much potential for me to say anything positive about it.

DrFell··on Deno 1.10 Release Notes
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
DrFell··on I finally escaped Node
Most Node devs are JavaScript monoglots, who just recently learned frontend, and figure "Let's use JavaScript for everything!"
DrFell··on How an Anti-TypeScript “JavaScript developer” like me became a TypeScript fan
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, and running it in a JavaScript engine on a server. That's only necessary in a browser.

On a server, if you don't want to use JavaScript, you can just directly use a classic OOP language, and dispense with the whole extra frontend transpilation abstraction.

Unless you're a frontend-only webdev, and, understandably enough, you don't want to learn a classic OOP language, which I believe is the real reason.

Or, at least I hope so, because the only other possible reason is mass obliviousness, and that's horrific.

DrFell··on How an Anti-TypeScript “JavaScript developer” like me became a TypeScript fan
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 that JavaScript developers are starting to use TypeScript on be backend, i.e. Deno.

You are using the patch to JavaScript that backend devs needed to make JavaScript more like backend languages in the very place that the languages it is trying to be like already exist. It's ludicrous.

DrFell··on Using ES Modules in Node.js: A Practical Guide (Part 1)
It's sad to see a serious thread about Node.js here, complete with mention of using TypeScript on the backend. Taps
DrFell··on I don't want to do front-end anymore
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 with, and maintain long term.

The reason is because the easy stuff its too simple to have an architectural foundation or engineering vision. Easy to learn, hard to use. Sort of the learning curve version of a stitch in time saves nine.

It's exacerbated in frontend because it attracts so many beginners. When the loudest voice is the junior developer, popular tech != good tech. That's why frontend is so chaotic and confusing.

This is all sort of obvious, but nobody want's to hear it. When I've tried to state it in online forums, I'm either a troll or a gatekeeper. shrug

DrFell··on Developers spend most of their time figuring the system out
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 abstraction to 'fix' that nonissue. Whatever. I can avoid it for as long as I can see to care.

DrFell··on Open-source, not open-contribution
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 experience?

It sounds mean, but the trend should probably be discouraged. It's unnecessary, anyhow. Open-source projects are not practice projects. You make those up yourself.

DrFell··on Offbase: Static site generator in a browser
I still think a plain old PHP site works just as well, and is easier and more flexible than any SSG system.
DrFell··on Hotwire: HTML over the Wire
That's good, because I've been deliberately ignoring pop webdev technology in hopes this would happen.
DrFell··on Vercel raise $40M Series B
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.
DrFell··on Angular 11
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 much. I'm a better developer today because of it.

Thanks, Angular!

DrFell··on The Return of the 90s Web
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.
DrFell··on How and why GraphQL will influence the Sourcehut alpha
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, databases, and security are a big scary unknown they are too lazy to learn.

A big project cannot afford to ask for high standards from frontenders. You need a hoard of cheap labor to crank out semi-disposable UIs.

DrFell··on Most tech content is bullshit
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 of thumb has practically become a mantra, and enables this. Newer developers who grow up in the online community are so afraid to think for themselves, lest they get mortified to death for doing something dumb. So it's sort of a self-perpetuating complexity problem.
DrFell··on Microsoft: We were wrong about open source
How corrigible of them. We all know damn well they have no choice.
DrFell··on 17yo guy built 14.7“ f/2.89 Newtonian reflector telescope
He didn't grind his own mirror, though. If you want to be a real ATM, you gotta make the mirror.
DrFell··on From Node to Deno
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, then transpiling that to JS, then running that in V8 on a server, you have taken a big step into the Rube Goldberg dimension.

DrFell··on Deno 1.0: What you need to know
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 scripting technologies outside the browser are starting to seem like even more effort.

Plus, those efforts yield skills that only apply within the contrivance. A second language would apply more broadly, and probably be more edifying.

DrFell··on Deno 1.0: What you need to know
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 hey, that’s life in a browser.

So if you’re not stuck in a browser, and can run any language you want, why in the world would you do all that?

DrFell··on Problem of Time
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. Now is a slice through the cosmos that really exists. I have had thoughts about how relativistic effects work with that, but I honestly think I went far enough. I leave that to others to think about or scoff at.
DrFell··on Problem of Time
Clocks appear to tick because we are locked in a series of moments. The clock exists at all times it has or will show.
DrFell··on Problem of Time
Causality, I guess would be my answer there.
DrFell··on Problem of Time
The problem of time comes from the notion that we are matter existing through time, instead of realizing sentience is made of events.
DrFell··on Show HN: Hacker News Trends
Ah trends, the modern replacement for getting it.
DrFell··on Copying data is wasteful, mutating data is dangerous
I have been mutating data for decades without any unexpected behavior gremlins.
DrFell··on Urql: a GraphQL client library
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.
DrFell··on Urql: a GraphQL client library
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. Plus, just wait, jeez. Don't blame the separation of the work into roles for your problems, it is usually good, and often necessary. Then again, if you're full-stack developer, you can just go fix the endpoint yourself.

I know the argument about over-fetching with an API is that you have to make one call, than loop through and make secondary calls, but you can mitigate that, it is rare, and is actually fine. Ad-hoc data modeling encourages over-fetching in it's own way. You always make in-situ calls for exactly the model shape you need right there. "That model is not quite the shape I want, I will do another query." Plus, with pre-defined data models you can save them, in like a state object, they are more reusable. You can even use them in a totally different program.

← PreviousPage 2 of 3Next →