I am so tired of Linux users who scream “I use X btw” everywhere… Like maybe it was cool some decade ago, but now it’s just annoying seeing it wherever I go. I hope Photon will eventually feature content filtering by keywords.
Imagine your identity being what OS is on your computer. And I’m a Linux sysadmin lol
Also Linux people bash Windows server but it’s actually getting pretty good. I am running some server 2022 instances right now and they just work. I was tasked to make a gold image but I found basically nothing to strip away from the install out of box. Try it before you bash it.
Free and open source software are good examples of an alternative to the way we manage labor today. Wanting gay space communism is as much a part of my personality as me liking Star Trek and Linux. Moreso theyvare part of the same coherent picture.
The very nature and origin of Windows is part of the problem.
Going Linux is as much of a political choice as it is a practical one. Software must be free, and Linux shows it very much can, while remaining practical up to the very enterprise level, data centers and supercomputers. and while we normally don’t think of enterprises as champions of free software, their influence is essentially the greatest.
Been hearing that since the 90s, but win NT is actually pretty good, it just works. Nah thanks, I’m no longer a sysadmin and haven’t tried Windows past 2000 server I think, but unless you are stuck with running Windows specific stuff (it was sql server for me at the time), and assuming you have a say in the company/project you work on, why bother?
One thing I learned about Lemmy is their users are much more serious. There’s a lot of obviously sarcastic comments getting replies treating it as a serious comment here.
Dev Home is a new control center for Windows providing the ability to monitor projects in your dashboard using customizable widgets, set up your dev environment by downloading apps, packages, or repositories, connect to your developer accounts and tools (such as GitHub), and create a Dev Drive for storage all in one place.
Use the centralized dashboard with customizable widgets to monitor workflows, track your dev projects, coding tasks, GitHub issues, pull requests, available SSH connections, and system CPU, GPU, Memory, and Network performance.
Use the Machine configuration tool to set up your development environment on a new device or onboard a new dev project.
Use Dev Home extensions to set up widgets that display developer-specific information. Create and share your own custom-built extensions.
Create a Dev Drive to store your project files and Git repositories.
I have no other skills that would pay anywhere close to what this career pays. I’d need to go back to school and become a surgeon or something. I don’t think they let people become surgeons at 50 years old, and I don’t have the energy for an internship and residency. I’m just hanging on and hoping that it doesn’t all vanish in the next few years. I’m also spending time learning how to leverage AI, since I think that’ll put me a step ahead. Good luck to all of us, we’re going to need it!
You have to listen to your heart, at least once in your career, to learn that grass on the other side is covered in just as much dog shit as it is over here.
I’ve known people who do this several times in a year. One even came back to his old job, just to leave it within months to go to a new one, brag about how much better it is. He moved on from that job too within a year.
Might just be the entire industry has reached enshittification in more than one way.
To me, a corporation cannot maintain quality code because requirements are ill defined, and there is no “done” state. With those two conditions present, unable to be changed, it’s not possible to form a coherent codebase. Those who try will make things worse, because their abstractions won’t fit in a year or two.
This is exactly the “messy code” people then leave behind. Bad code can come about for other reasons too, of course, but this is one of the more annoying reasons, because someone wrote it with self-righteousness, as if they were the only people to truly SEE the problem. Sigh.
It’s fine, this is how enterprise works. You can learn to navigate and make a living from it. You MUST internalize and accept that it is NOT the same as maintaining code for an open source library or whatever people think it’s going to be.
Usually a call sign of someone who hasn’t been really entrenched with bad code to understand their foolishness in comparison.
I’ve only seen people hold that idea if :
New and amateurish, I give them a chance cuz they might learn. But let them learn.
Someone who’s only ever worked in maybe two places for very long lengths of time, given way too much power too early, people threw around ‘genius’ too eagerly and these people guard their code like a watch dog likely because it’s so fragile a simple ‘()’ in a string will bust everything . No one else can work on it and the only way you can fix it is the moment they leave. They will not learn. You can only hope the eye of Sauron will stop looking in your direction.
I’m English, not American but I see it as Saturday and Sunday are the two ends of the week. Like how a string has two ends. The weekend is both the start and the finishing end of the week.
So, when someone asks if you are free the next two weekends, you assume they’re talking about the next Saturday (tail weekend) and the next Sunday (front weekend)?
I’m refering to end in a temporal sense because we are talking about a time context here. There is a clear direction so going backwards brings you to the begin.
Sometimes that’s part of the issue (or the whole deal), but sometimes it’s not even that.
Sometimes it’s that someone asked something difficult and elaborate to answer, which has been answered a ton of times, and it’s tedious to answer again and again. But if someone answers with misinformation or even straight FUD, then one needs to feel the urge to correct that to prevent misinformation.
I suffered that with questions in r/QtFramework. Tons of licensing questions, repeated over and over, from people who have not bothered to read a bit about such a well known and popular license as LGPL. Then someone who cares little for the nuance answers something heavy handed, and paints a wrong picture. Then I can’t let the question pass. I need to correct the shitty answer. :-(
I would say that if someone asks a difficult question it’s often difficult because it’s very general, so you don’t have any specific point to answer that you know will satisfy the person asking.
On the other hand, if someone is writing misinformation then they provide specific statements which still may be difficult to correct but you have those anchor points you can refer to.
So I guess the thing here is that if someone, after asking a question, writes a BS answer they actually refine their question and narrow its scope, thus making it easier to answer.
I usually see broad questions about rather simple things unanswered, but very specific yet difficult questions answered
Thanks! In computer graphics it’s referred to as the “Utah teapot” because the 3D model was created at the University of Utah. But it was originally a Melitta brand teapot. It is still manufactured by German company Friesland, which I bought it from.
Unfortunately it appears they recently had a fire and their webshop is temporarily closed, but I think you can also get it off of Amazon.
I’m more of a computer-science geek than a tea geek, so all I can say is that it pours without spilling. You won’t get a laminar flow out of it or anything like that.
I think there’s a positive coming from this competition, though. Apparently this infighting has re-lit the want for type annotations to be embedded in vanilla JS (ECMAScript proposal). I feel like this would be the ideal scenario: things working right out of the box without needing a compile step or additional tooling.
You can get as close as it gets to this experience by using alternative runtimes such as Deno or Bun, which have native TS support (meaning you can just execute a .ts file without having to transpile it), but of course as soon as you have to write code for a browser you are back in the middle ages.
Depending on how it pans out, it’s either not useful enough. Who the hell doesn’t use namespaces or enums. Or - as
These constructs are not in the scope of this proposal, but could be added by separate TC39 proposals.
implies - a door opener to outsource TypeScripts problem unto other peoples and not to investing into improving WebAssembly. That’s just MS being lazy and making their problems other peoples problems.
I feel like this would be the ideal scenario: things working right out of the box without needing a compile step or additional tooling.
It’s just annotations. No proposed semantics of a type system which your browser could check on its own.
Uhhh, typescript devs? Enums were useful once, but typescript evolved everything else around it and these days using direct values is actually far better.
And I don’t think anyone uses Namespaces other than for defining external modules.
My bad, I’m not deep enough into our frontend stack to realize Hjeilsberg already did what he does best - ruining enums. (I guess he is not to blame for global imports in c#, so i can not add ‘questionable import module/namespace ideas’.)
And it seems like this proposal contains type declarations (in order to compensate for their enums), among other typescript specific things. So, guess it is option B, then.
Yeah it’s interesting because JS is interpreted, not compiled. The proposal allows for type annotations in the syntax but no actual interpreter consequences. On the one hand that makes sense because otherwise you’re in the territory of runtime type-checking which would be a huge performance hit and would sort of defeat the purpose of static types anyway. But that means you still have to rely on your IDE or a linter for this to be useful.
I don’t see any practical use case for it as is as anyone wanting to use them would want the full TS feature set anyways, but I could see it being a good step forward for more meaningful features to be added in the future.
That’s part of why it took so long. Every day I thought I was done a new person would be added to the review and they would identify a security and/or use case edge case.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.