Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)FO
Posts
0
Comments
107
Joined
2 yr. ago

  • Toyota and Honda have the reputation for being the most reliable. I would add Subaru to the list as well out of my personal experience.

    Although, I think the best investment a car owner can make is a basic set of tools and the time to learn to do repairs/maintenance yourself. I started by doing my own oil changes and, at first, it wasn't cheaper at all with needing to buy the tools, but in the years since I think I've become quite a handy mechanic and have saved tens of thousands by doing everything myself. There are repair videos online for virtually everything so it's pretty easy to get started with basic stuff and work your way up from there as needed for your car.

  • Alright, I'm not going to get into an internet pissing contest over front end techniques since despite being in the industry for over a decade I've been deemed oblivious and misinformed based on two comments. I'll keep doing things my way and you can do it your way. I'm not going to lose sleep over it or resort to calling names over a comment on the internet of someone's opinion I don't agree with.

  • Is it not generating HTML on the server to be served to the client? What you're describing is, in my opinion, an overly complicated form of dynamically rendering HTML on the backend. It's exactly what I'm talking about: the layers and layers of complexity modern web development has added hasn't really solved any problems but rather primarily created problems which are solved with another layer on top as a fix which has problems of its own, and repeat.

    Anyway, that's my opinion on the matter, I've toiled with modern web development tools my fair share and time and time again found that removing all of them in favor of vanilla JS where strictly needed and traditional dynamic backends is the most reliable and performant, and frankly enjoyable form of web development. I know others like those workflows and the complexity/power they bring and that's fine, it's not my cup of tea though.

  • Because it's easier to compare yearly salaries. If you say “I’m making 50k” then I can assume it's yearly (if it's monthly then good for you, but that's overwhelmingly not the case). Otherwise you need to specify the pay frequency and do math.

    Same with net/gross. I can assume your yearly salary is given in gross because net introduces a bunch of variables with tax rates based on location/deductions that makes it a fairly meaningless value to compare against. Not to mention your net monthly income may change in a year as you hit certain tax limits like the max social security tax limit.

    Some people may also not have consistent monthly earnings so averaging income over a year gives a more accurate picture of average income.

  • The mere existence of the term "server-side rendering" illustrates this well. I remember the first time I read about that concept and immediately thought "you mean the way we've been writing websites since the 90s?"

    Maybe I'm just out of date, but IMO web development has completely lost its way. I don't do much frontend work anymore, but when I do my goals are always to see how few JS libraries I need to use and how little JS I need to write in general. The end result of that plus doing all/most work on the backend, sticking to standard HTTP conventions, and using only vanilla JS means super fast and performant websites with fewer bugs, less constant deprecations to keep up with, less security vulnerabilities in all the JS libraries, and no constant headaches from a complex Webpack-style build system for assets. It's actually quite enjoyable when you remove all the bs of modern JS frameworks from your workflows.

  • Heh, I was about to comment how my hot take is that Python is overrated. It's... fine and I don't really have anything against it for the most part, but I greatly prefer Ruby to Python.

    I'm speaking purely about the language itself here, not any libraries available for it (since someone will always point out how great Python is for data work).

  • Yes. I bought a manual car a few years ago having never driven one before. I taught myself how to drive it in my driveway and with the help of YouTube videos. I really enjoy it and hope that even in the future when EVs are the final nail in the coffin for manuals that I still have at least a "fun" car with a manual. I'm in the US and a millennial.

  • To add one more option as well: In even more limited cases, a fanbase is dedicated enough to rewrite the entire game into free software like with OpenRCT2. I don't know if I'd really call this a "mod" per se since it's an entirely new implementation, but the end goal of changing/customizing the gameplay remains the same.

  • I get it if the goal is to explore ideas, but any serious proposal that starts with "get rid of TCP/IP" isn't a serious proposal because that stipulation alone makes it dead on arrival. Unless you could convince major internet backbone providers to adopt a complete replacement because of fantastically convincing reasons, dropping TCP/IP simply isn't going to happen. Case in point: we've had a pretty damn good reason to migrate from IPv4 to IPv6 for decades now and we all know how well that's going.

  • That's fine and all, but if TCP/IP is no longer in play, how would a network like this even get started? The ISPs won't support it and there would be no way to connect nodes other than go to back to sending tones over phone lines or attempt some type of mesh network.

    By the way, Internet 2.0 already exists: https://en.wikipedia.org/wiki/Internet2

  • Right, that's why I put the "within reason" in my comment. You still need to guard against malicious inputs so ultimately there is some max length limit, but it should be way beyond what a reasonable password length would be.