Agreed, my wife and I had that conversation recently, as it happens. Though, for some things, there are other benefits. Herbs is the best example, even the fresh, packaged herbs that you can buy at a grocery will be noticeably not-as-good as something that you picked fresh in the backyard 2 minutes ago. Dill, basil, thyme, mint, what have you. I’ve found the same to be true of things like bell peppers and jalapenos.
Was intrigued until step one of “Getting Started”:
Install Node.js 20 LTS
That’s gonna be a “no” from me.
I had the exact same question, did the exact same thing, and had the exact same response. EVERYONE does this, it’s infuriating. If you’re going to have a public-facing info page about your project or product, you need to assume that people know NOTHING about it.
KeePass on my phone and desktop, with the master file sync’d automatically to the server in my basement.
The XZ exploit was found because some dude was investigating performance issues in a system, and noticed an unusual amount of time being spent in SSH processing, IIRC.
So, you’re a tech nerd who wants an addictive game?
Factorio.
Also Satisfactory, but I’m not sure how well it runs on Linux. Fairly sure Factorio will run on just about anything
Windows 11 has ads NOW, in the enterprise install I’m provided at work.
MLB 66
I think it’s a fallacy to say that you can or should build an application layer that’s completely DBMS agnostic. Even if you are very careful to only write SQL queries with features that are part of the official SQL standard, you’re still coupled to your particular DBMS’s internal implementations for query compilation, planning, optimization, etc. At enterprise scale, there’s still going to be plenty of queries that suddenly perform like crap, after a DBMS swap.
In my mind, standardization for things like ODBC or Hibernate or Entity Framework or whatever else isn’t meant to abstract away the underlying DBMS, it’s meant to promote compatibility.
Not to mention that you’re tying your own hands by locking yourself out of non-standard DBMS features, that you could be REALLY useful to you, if you have the right use-cases. JSON generation and indexing is the big one that comes to mind. Also, geospatial data tables.
For context, my professional work for the past 6 years is an Oracle/.NET/Browser application, and we are HEAVILY invested in Oracle. Most notably, we do a LOT of ETL, and that all runs exclusively in the DBMS itself, in PL/SQL procedures orchestratedbbybthe Oracle job scheduler. Attempting to do this kind of data manipulation by round-tripping it into .NET code would make things significantly worse.
So, my opinion could definitely be a result of what’s been normalized for me, in my day job. But I’ve also had a few other collaborative side projects where I think the “don’t try and abstract away the DBMS” advice holds true.
I’ll take this over the more “classic” styles, when people seed to believe they were paying the compiler by the character.
You mention Bally and baseball, mlb66 was my go-to last year.
Generally speaking, fault protection schemes need only account for one fault at a time, unless you’re a really large business, or some other entity with extra-stringent data protection requirements.
RAID protects against drive failure faults. Backups protect against drive failure faults as well, but also things like accidental deletions or overwrites of data.
In order for RAID on backups to make sense, when you already have RAID on your main storage, you’d have to consider drive failures and other data loss to be likely to occur simultaneously. I.E. RAID on your backups only protects you from drive failure occurring WHILE you’re trying to restore a backup. Or maybe more generally, WHILE that backup is in use, say, if you have a legal requirement that you must keep a history of all your data for X years or something (I would argue data like this shouldn’t be classified as backups, though).
Damn, actual personal growth being displayed on the internet? Such a rare thing I find myself wondering it wasn’t all staged. How messed up is that?
Also, how messed up is it that it worked, cause I’mm’a go watch all of these.
I know folks in the C# Discord have talked about getting WinForms to work on Linux, you could post a question there. But unless you’re specifically dealing with maintaining some legacy app, you should not be using WinForms, much less on Linux. Avalonia or Xamarin are definitely the way to go if you’re making something new and want cross-platform desktop support.
Protip if you do go down that route: Tutorials tend to ignore the fact that you don’t have to use XAML to make anything in these frameworks. You should. But if it’s more comfortable for you to write WinForms-style imperative code that you’re used to, you 100% can, the APIs are not significantly different.
Can I get an Oracle version?
There was a Payday 3?
Apparently trained on 4chan?
Why the hell is a professional tech business not relying almost-exclusively in ethernet, anyway?
Discord gained popularity and maintains it, in spite of the many reasons to avoid it, because of usability and feature richness. Slack, Teams, Matrix, Telegram, they are miles ahead of everyone else in the live-chat space, when it comes to user experience.
This was an interesting article about some tech I’ve never heard of before, but it has little to nothing to do with Discord’s overall success.
Absolutely. Like you say, it just doesn’t happen in large streams, and the threshold is probably a lot larger than you think, since on average maybe 10% of viewers actually participate in chat. The dynamic starts shifting at around 1,000 simultaneous viewers, in my experience, between chat being readable and interactable, and being just spam. That’s still plenty big enough to qualify for partner, and even make a living off of streaming alone.