Nowadays, both on my previous and current job, we go for Debian slim. Works perfectly and is worth the extra bytes.
I will also never use alpine again :-)
244 karma · joined March 2, 2013
Nowadays, both on my previous and current job, we go for Debian slim. Works perfectly and is worth the extra bytes.
I will also never use alpine again :-)
What? :-)
Apt is by far the easiest way o install and keep software updated.
Compared to app-store, homebrew, and toy like solutions for Windows.
Usually when you have that many tabs open, it's not because you read/work on the pages.
But for business logic, database interactions, calculations, etc, I really think the language construct is to clumsy and does not scale nicely.
I really don't see how anyone choses nodejs/deno to anything.
Java imo gives you much less trouble, is more stable, has a working (!!!) Unit testing setup and exceptional runtime.
Next on my list is to give rust a go, since I'm intrigued by its features, but if I was to go fast I'd go with java any day.
The ux is terrible, and on Mac there are at least three different UIs you can open (browser, click on toolbar icon and "full" UI.) On Linux I think there are at least two variants, maybe more, dont remember.
Just make one and make it simple and usable. By simple I don't mean Google/apple-style "hide everything because people are stupid". I mean simple, consistent, reliable, usable and powerful.
BR
It's not the UI is very complex , or that there are ton of frameworks with different maturity levels.
It's because the browser and thus html/CSS was made for documents.
If we made a "browser" made for apps, where we didn't need to transpile to js, and didn't need to cater for incompatible browser versions, but could concentrate on what really matters we wouldt have such a big problem
I used to use nxinx plus, but after moving to a new company and trying to purchase it again, not only had the price quadrupled. I also wasn't able to actually buy a license without four meetings, a shitload of mails and a lot of frustration.
In the end I gave up and kept the community edition while I explore the options.
Nginx clearly moved from the cheap and performany segment to the expensive and cumbersome.
It's an improvement of our toolbox, students SHOULD learn to use it.
It's not much worse than using c instead of assembler, or java instead of c, or ...
Throughout time people have invented new tools that makes their predecessors more efficient in their proffesion.
Too many programmers these days behaves like the workers did when automatic looms were invented. Or when the chainsaw was invented.. or the computers.. or the...
It can be tricky to make everything self explanatory, but at least if you use icons or text rather than just colour you give the brain something to help you recognize.
What I did notice though was th first screenshot with the red, yellow, green buttons of osx window titles.
I think this is a really bad design, and I don't understand how people can like this.
Sure, nice round "buttons", but very unclear what their purpose is.
I think this is something of a red line through Mac/iOS: The preference of unclear user interface that "looks good" instead of a clear interface that communicates with the user.
I've used Mac for years, and still don't know what the yellow button does.
I like the idea of this new OS, but please make better design choices that Apple :-)
You should stay and make a change.
However, I have a rough time buying into apps that are built for one platform only.
I move daily between Mac, Linux and occasionally windows and want the tools I put time and money into to be available in all platforms.
Could you please elaborate on what learning "sight words" mean?
I'm a little bit concerned my daughter might have dyslexia, but she is too young to be evaluated according to the standards here.
Anything I can do to help her pick up reading better would be appreciated.
At the end, concludes with:
> Mechanical watches are not as accurate as digital ones. They require maintenance and are more fragile. Despite all these drawbacks, these devices show a true mastery of engineering. With creative use of miniature gears, levers, and springs, a mechanical watch rises from its dormant components to become truly alive.
And to an extent, I can agree that figuring out and building such a tiny mechanic is truly genius. But so is figuring out the digital electronics devices, even if they seem much less sexy.
What we should really be thankful for are those geniuses who figured out all those technologies and put their powers in the hand of the mere mortals.
I don't need to be able to understand the inners of the computer, but can still make use of its power to the benefit of others.
API/request level testing is great when appropriate, but testing what happens in browser won't be possible without using something like selenium, nightwatch or playwright
Just remove them completely and let you window manager manage your windows.
(And yes, Firefox still supports browsing without tabs, so we got what we need right there ;)
First time it took a lot of effort to pinpoint the problem.
Second time too, since it appeared because of a non-relevant code change (which lead to slighty more DNS requests).
In both cases, a simple switch to Debian slim saved the day.
Alpine is since banned from any env I'm working in :-)
Which brings me to the next topic: profiling nodejs apps... Any tips there?
Maybe because I built SPAs already pre -10 and I think that finally (as Vue entered the scene) even frontend development can be fun, structured, testable, etc.
But the reason I write is this: When it comes to SSR, I still think node/js is absurdely slow.
Compared to almost any java rendering backends, where I'd expect no more than 50ms response time/thread I see 200-300ms/instance of nodejs.
What are your experiences? I'm I just doing it wrong :-)
Those tasks that I use bash for are usually one-offs, and live on the server they are used on.
Thus, it should be easy for the next admin/Dev to find it and understand/fix/extend it.
Of course, if there is a more advanced task those requirements fall short and there should be a proper Dev env with source control, tests, etc.
- Self contained in one file
- Easily edited with vi/nano (i.e. through a console ssh session)
- Readily available on most Linux base installations
- No crazy runtime installation requirements
Edit: formatting)