Hacker Newsnew | past | comments | ask | show | jobs | submit | Kab1r's commentslogin

Is there a good reason (other than licensing and Linux as an alternative) I shouldn't use Windows Server 202X as a Desktop OS?


I've heard tell that some software out there will refuse to operate on Windows Server because of licensing, like perhaps they want you to get a business license. I have no evidence at hand, but something to look into.


I worked at a software vendor where we would check the type of product and yes you needed our server product to run on their server product, whether or not you used the server as a server.

Not all software does this but I also don't recall it being unusual.


You don’t need to use the Server SKU. LTSC exists. It’s basically the Server version, but without any of the Server stuff.


To be pedantic, Server 2022 is a newer build than any Windows 10 version.


For Windows 11, all editions (11, 11 Enterprise LTSC, Server 2025) are 24H2.


IDK about today but back when I hard work that required Windows that's how I stayed sane.


These days there is no reason to use Windows at home. Just move to a distro like Mint or Ubuntu. It will save you money and help stop filling up Landfills.

I am on a 10+ year old Laptop with Slackware, for desktop use it is just as fast as any modern Laptop with Windows, I would even say it is faster.

Also you will find Libreoffice is just as good as M/S Office. Just ignore the fud. FWIW, I believe many foreign countries will start migrating to Linux and I heard that is already happening in China.


> These days there is no reason to use Windows at home.

I have two, sadly.

1. I use my Windows PC for flight simulators. While many simulators will indeed run under proton, the hardware devices (VR, joysticks, throttles, pedals, panels, etc.) usually will not, or at best run with minimal functionality.

2. I develop cross-platform software and need a Windows PC to test that environment.

A third for some people:

3. There is no great alternative to certain visual media software. e.g. Affinity Photo/Adobe Photoshop has no equivalent on Linux. No, GIMP is not anywhere near equivalent- in the same way that Nano is not equivalent to Visual Studio Code.


To add onto 3, I do my taxes every year using either the desktop version of Turbo Tax or H&R Block. They only make Mac or Windows versions of their software.

I've read online that people have attempted to use wine in order to emulate the Windows environment with no success.



I use FreeTaxUSA for my taxes, works great for me.


> These days there is no reason to use Windows at home. Just move to a distro like Mint or Ubuntu. It will save you money and help stop filling up Landfills.

Old Intel based computers are terrible for power usage. Modern computers that are ARM based are much better for the environment.


> Modern computers that are ARM based are much better for the environment.

And modern computers that are Zen based are even better. You can do real work on them, instead of sitting idle all day. /s


> S3 launched as the first public AWS service.

Didn't SQS launch publicly earlier than S3?


SQS went into beta first, S3 went "GA" first.

AWS typically considers the "GA" milestone as the "public launch" date, which is silly because the criteria for what is good enough for GA has changed over the years.


> RAID or do regular off-site backups.

RAID is not a backup! Do both.


Does anyone know if this is the same vulnerability that ASUS leaked in a beta BIOS?


To the very best of my knowledge, yes, it is.


Being grateful for a miserable life marginally improving does not negate otherwise unavoidable prolonged suffering.


I would call this a compiler bug



If the change is targeting a rust edition it's being treated as a feature/improvement not as a compiler bug. If there isn't a spec that explicitly says that this is expected behavior (and as far as I know there isn't a concrete spec for the rust language) it should be instead treated as a backwards compatible bug fix


No, it's being treated as a breaking change, which it is. It is not a backwards-compatible bug fix.

You are correct that there is no concrete spec for the Rust language; the current state of the compiler and stdlib is the "spec". So this is a breaking change to the "spec", and requires a new edition.


It's very much not backwards compatible, that's why they are doing it in an Edition.


Grace Hopper already includes Arm based CPUs (and reference motherboards)


Am I the only one that really dislikes the syntax choices here?


I feel like there is a specific kind of person that likes all this, and there is very little overlap between those people and the people that choose to use Typescript.

Kinda feels like someone was forced to work in Typescript and really wanted to scratch their own itch.


I must be a very specific kind of person. I love TypeScript, and loved CoffeeScript even more. I’m baffled by many of the comments here and excited to try Civet.


Nailed it


It appears to prioritize easier and faster typing over readability, which is a poor choice as programmers spend more time reading rather than writing code.


Strongly agree. This is unreadable, and find it hard to believe they included this as an example of something someone would want to do:

    value min ceiling max floor


Having worked in Rust I love the pattern matching proposal. Having dabbled in Swift I like the single argument function part (though keep the brackets, please)

Much of the rest I could take or leave… but then is that just because I’m not familiar with them? Stuff like the pipe operator makes sense to me but it reminds me of .reduce(): there are a few legitimate uses of it but the vast majority will be entirely-too-smart—for-its-own-good show off coding.


I fell in love with pattern matching the first time I used Haskell. Having the feature is great, but I really don't like the syntax used here.


Nope! I'm also not convinced by it.


Either this or they worship Progress and Poverty like a lost religious text


Is this just searching certificate transparency logs?


I'd imagine it's a combination of

- CT log monitoring (https://github.com/CaliDog/CertStream-Server)

- Mass-Scanning across ipv4 on 80/443 at the least?

- Brute-forcing subdomains on wildcards with large DNS wordlist (like something from assetnote: https://wordlists-cdn.assetnote.io/data/manual/best-dns-word...)

- Scraping/extracting subdomains/domains from JS

But I've never attempted to enumerate subdomains on this scale before, so I could be missing something obvious


I think it's a mix of different sources. Certainly, some of my subdomains there never had an SSL certificate.


Well, CT logs are a data dump, they are not searchable, ingesting all that data near-real time and making it searchable in a useful and fast way (especially with wildcards) is actually quite challenging!


Where does one ingest them from?



Thanks!


I have subdomains with (non-wildcard) certificates that aren't on there.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: