Earlier quoted context omitted.
I agree ansible is bad, but it is NOT the state of the art. Honestly its kind-of old and dead at this point replaced by stuff like CDKs. Programming in YAML sucks. YAML based solutions will always come up short because you cannot develop proper abstractions so you end up with a big bowl of copy-pasta amd indecipherable work-arounds. IMO the modern web is all based around adding types to systems because we've realized…
What are CDKs?
Everything Easy is Hard Again (2018)
61–70 of 269 posts
Re: Everything Easy is Hard Again (2018)
#62Frank is right, of course. Staying up to date with the tooling, best practices, and user expectations of the web requires an unreasonable amount of attention if making websites is only a small part of your service offering. One reason I prefer frontend libraries like Vue and Svelte is they feel closer to the grain of the web (HTMLesque templates with JS and CSS sprinkled in), and provide a reasonable level of abstrac…
And this is exactly why any of my hobby projects that involve JS are done with plain JS, with as few libraries as possible. I might pull in specific libraries, but I don't want to pull in a giant framework that will be outdated the next time I decide to work on that particular project.
Re: Everything Easy is Hard Again (2018)
#63Earlier quoted context omitted.
Hah: I am very particular about fonts myself but what bugs me most isn't sub-pixel hinting (which is "good enough" with the latest freetype IMHO) it's the size of fonts. Windows is so far off the mark on 99% of computers and it drives me crazy! Repeat after me: 72pt is one inch tall! 72pt is one inch tall! 72pt is one inch tall! The "point" scale of fonts is actually a precise, real-world measurement like inches, mil…
I have never seen a display with non-square pixels, except maybe on cameras. Where are those typically installed?
Re: Everything Easy is Hard Again (2018)
#64Confession: as a recovering programmer who made a career change to non-programming, it took at most 30 minutes to say "fuck it" and go with Squarespace. I've never been on the web side of things, but I knew enough HTML in the early aughts to put up a basic informational website. After digging in to some sites I admired, I decided that it was too much distraction from my actual work to roll my own. Granted some of thi…
Re: Everything Easy is Hard Again (2018)
#65It's somewhat amusing to see people complain about the supposedly increasing complexity of web development. Sorry-not-sorry it's not that bad or even that complex. In fact things are far easier and less complex then they were just a few years ago and improvements continue at a rapid pace (modern browser module support, vitejS, ESbuild). I don't even need to use babeljs anymore whereas just a few years ago it would have been required for cross browser support.
Developers as a cohort love to feel themselves and ego trip about how smart they are until they hit something they don't understand immediately and suddenly it's too complex and they have to write 5k words bemoaning webpack configs as the worst thing ever.
I think the problem is actually the opposite and things are way too easy now because, like anything in life, effectively simple web development requires self discipline and simplifying abstractions like React make it too easy to just throw shit at the wall and see if it resembles a working webapp and then I end up having to maintain a lot of seemingly working apps that are an absolute mess of tightly coupled spaghetti code with no clear architectural design whatsoever but product thinks it works because the side effects show up at the right time.
Re: Everything Easy is Hard Again (2018)
#66Earlier quoted context omitted.
And this is exactly why any of my hobby projects that involve JS are done with plain JS, with as few libraries as possible. I might pull in specific libraries, but I don't want to pull in a giant framework that will be outdated the next time I decide to work on that particular project.
Another thing I find weird is how bloated static typical site generator tools are. The delivery medium of static HTML is timeless. But the odds that a static site generator with dozens of dependencies will still work N years from now? Grim.
Re: Everything Easy is Hard Again (2018)
#67Confession: as a recovering programmer who made a career change to non-programming, it took at most 30 minutes to say "fuck it" and go with Squarespace. I've never been on the web side of things, but I knew enough HTML in the early aughts to put up a basic informational website. After digging in to some sites I admired, I decided that it was too much distraction from my actual work to roll my own. Granted some of thi…
what kind of work did you get into after programming out of curiosity? rare to see people go the other way
I suspect this is literally true, but only because we don't see them. I've heard second-hand the story of a top developer at a famous unicorn who just couldn't keep up with all the stimulants everyone was using to code more and burned out, bought a cabin in the woods, and became a hermit.
Re: Everything Easy is Hard Again (2018)
#68I'm going to get downvoted into the the ground for this, but I think it has to be said: Front-end infrastructure and tools design unfortunately does not attract the cream of the CS graduate crop (and even less so Front-End design work). For some reason, cream of the crop CS graduates usually veer towards systems, compiler, DB, back-end infra, language design, back-end, ML, etc ... But not front-end. The net result: t…
If you take a look at the labor demand for skilled front-end engineering (https://www.levels.fyi/), it's hard to come to any other conclusion than that major companies pay a lot of money for top talent. So if major companies pay a lot of money for that talent, either they're making profit from a very tricky coordination of skilled labor, or you're pulling an argument out of an opinion that is at odds with the reality of the industry.
Why do that? It could be that you're not familiar with how skilled frontend practitioners operate in large companies. Maybe that's why you're extrapolating (incorrectly in my opinion) that a) the web frontend ecosystem is trash and b) that is evidenced by cream of the crop CS graduates (???) choosing backend over frontend. My question is, what does that have to do with the reality of frontend today?
Maybe it once was useful to consider why CS graduates gravitating towards one end or the other, but that division seems a little old in the tooth now. Good CS graduates these days have full-stack chops, and don't have too much trouble crossing devops, frontend, backend -- anything necessary to get the job done. So with that said, it's hard to consider your final conclusion anything than a rant about your own difficulties and preconceptions about frontend web development than anything:
> The net result: the front-end ecosystem looks like the first BASIC program written by a 10 year-old who just got his first computer: it's a mess, it's unprincipled, it's grown organically, it's driven by fashion and immediate business needs, it's an unmaintainable tarpit, and it's increasingly a nightmare to build with.
It's true that there's a lot of the front-end ecosystem that is super messy. But there's a lot of it which works a lot better in comparison to what was available a decade ago. Moreover, it's intrinsically gotten more complicated as mobile compute has gotten more powerful. Mobile has not just become a thing but achieved critical mass on par with desktop. There are enormously lucrative challenges involved with front-end these days, and who knows how much headroom is left in the industry? The modern phone's capabilities today are so far beyond what was possible even four years ago, that it's hard to consider these kind of rants anything beyond a lack of imagination.
How is it that the largest megacap companies of our time are using better frontend experiences it to accomplish increasingly more revenue efficient activities than they ever have before? How is it that newly fledged startups are using the leverage of good frontend experiences to grow to $1B faster than they ever have before? Is it possible that UX and psychology account for far more of technology's value than you may be considering? Just a thought.
Re: Everything Easy is Hard Again (2018)
#69Earlier quoted context omitted.
I'm an avid Linux user, completely unfamiliar with BSD. Could you shed some light on how it further removes abstractions? I don't mind trying it out by booting it from a usb
> Could you shed some light on how it further removes abstractions? By not running hundreds of useless programs, I guess. If you launch htop inside OpenBSD, it'll fill half of your terminal, and the rest is empty. The easiest way to try it is to install it on a virtual machine. You'll see that not much is needed to get to a point to launch firefox from an xterm.
Re: Everything Easy is Hard Again (2018)
#70I think one driver of this cycle is: 1) need for capability that old method doesn't meet, so new tool is made 2) dev working on both simpler and more complex sites, wants everything to use the same tools 3) even sites with simple needs now get done using tools powerful enough to satisfy needs of complex sites 4) experienced dev doesn't see a problem, because they are conversant with those more complex tools, and also…
I think you forgot one driver, which IMHO is a major one: Imagine you are just getting into the business and are confronted with complexities, which would let you come to a grinding halt for the next 6 months until you have at least a foggy idea of what is going on. (Angular, Elm, PHP, React, ...) And once you worked through your initial list of "need to know", 5 more have popped up, like a hydra where chopping off h…