Hacker News new | past | comments | ask | show | jobs | submit | rkv's comments login

There is no way that I can explain better than this: https://lwn.net/Articles/689856/


They create a policy to prevent the use of Windows laptops but they are unable to create a policy to enforce purchasing the correct Operating System?


Comparing Windows and macOS to Linux is moot and we should stop doing it. Linux has always been and will continue to be an ecosystem driven by various communities, and expecting everyone to agree on the same standards is silly.

The sooner we all begin treating Ubuntu and Red Hat Enterprise Linux as separate Operating Systems the sooner we can all move on from the "single standard" and "Linux on Desktop" debates. As an application vendor I always find it amusing when customers ask if we support Linux. My response is no, we don't support Linux but we do support Ubuntu 18+ and RHEL 8. Linux distros are so wildly different these days, not just in software but in ideologies, that this distinction is important, and there's nothing wrong with that.


Not in 2022 they're considered different Operating Systems. People have been developing AppImage, Flatpak and snap for a reason. They're being used and it's a thing.

Yeah, the year of the Linux desktop isn't coming, but it's not 2001 either. We've standardised onto a few technologies pretty much everyone adopt except the ones that want to be different: systemd, Flatpak being the most used cross-distro system, pulseaudio (and pipewire offers a 100%-compatible shim for it), dbus, NetworkManager and now finally with GNOME 42/libadwaita we can have even standardised UI design.

And like many other things frontend, things move at a pretty rapid pace. Ubuntu 18 is ancient, might be good for a server, but it's not a good idea to use that as a metric for where the Linux desktop is.


Samsung support is atrocious. Had a similar issue with my S9 phone where the power button suddenly got jammed and couldn't be released. They sent it back with the exact same reasoning: "Caused by physical damage". Well yeah, I physically press the button to turn the phone on and off, what do you expect. I don't understand how they are still so popular when they never help you with anything.


Out of curiosity, what config changes did you use on apache?


Same questions here. I’m not sure I would know where to start on those particular configs


Maxrequestworkers, server limit?


IIRC it was MaxRequestWorkers to 1500, and MaxConnectionsPerChild to 0 (unlimited)


> They shouldn't consist of everyone telling everyone else what they're working on.

It's a common habit people fall into when transitioning to scrum. An experienced scrum master should never let this happen though.


Something separate (ie. custom code). You can use "Inspect Element" in your browser to confirm.



> Transmeta tried it and failed

Author has clearly not heard about NexGen! They implemented a RISC architecture that code morphed x86 i586 design. They were then bought out by AMD who shortly thereafter adopted the design for their own architecture. Then Intel had no choice but to adopt NexGen architecture as well lool. We all use NexGen Architecture now. The most famous microprocessor no one's heard of. I only know because NexGen was based in Milpitas and that's where I live, so Milpitas Architecture is like hometown pride.

As for patents, Xed is tiny (only ~4kb) and it allows us to distinguish the which instructions belong to which microarchitectures, e.g. k8, sse3, sse4, avx. That gives us a clear accurate picture of the intellectual property rolloff, thereby enabling a fabless chip or emulator to simply ignore the encumbered parts of the encoding space. The tradeoff is you can't patent troll Intel (due to Xed being licensed Apache 2.0) and I think that's fair.


XED is an Intel project, the X86 Encoder Decoder, for those who don't know.

https://intelxed.github.io/


Nexgen was great, the lack of a FPU at that moment in time however was fatal at launch.

Quake was just starting to ignite the world and pentium performance at 486 prices would have done more, but no fpu... it ran NT fine enough although my memory wants to say Microsoft detected it as a 386 so that would have cut NT 4 out of the picture.

I thought knowledge of them was more common but I guess not


The TL;DR seems to be that if you restrict yourself to implementing an ISA from 20 years ago, your chip can indeed be patent free, but that isn't going to run modern software - maybe not even modern x86 32-bit software!


I thought windows runs on anything which supports extensions up to sse2, which is what amd64 includes.


https://docs.microsoft.com/en-us/windows-hardware/design/min...

Devices that run Windows 10 for desktop editions require a 1 GHz or faster processor or SoC that meets the following requirements:

* Compatible with the x86* or x64 instruction set.

* Supports PAE, NX and SSE2.

* Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW for 64-bit OS installation


Mmmh, so it seems one would be stuck on win 8.0 (for 64bit) with an original implementation of amd64. Could probably still run a lot of new software.


Or run 32-bit Windows 10 instead.


The PAE and NX requirements can be disabled in the bootloader.


2026. Six years to go.


> No support for null strings? Check

Why would you ever want this? Gives me Java nightmares.


Do you have statistics? My perception is the opposite.


Not directly, but anyone with a Hackintosh (modified PC running Mac OS) must have it disabled, and a fair number of pro users disable it for various purposes.


JFYI you can have SIP enabled on a hackintosh if you use clover to inject kexts.


Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: