So, Android?
5,063 karma · joined July 15, 2021
So, Android?
We used to do a lot of worse stuff too, like eat radium hoping for brighter skin.
It should be criminal to leak PII, and company leadership should face imprisonment.
Similar pet peeve, and I think the solution to this is the platform setting, adopting, and enforcing conventions. Something like what has happened with notebook trackpads[1] about a decade ago, and more recently RGB peripherals[2]—no more cancerous giant Electron app to move a few sliders and set an RGB hex code.
[1]: https://learn.microsoft.com/en-gb/windows/win32/input-precis...
[2]: https://learn.microsoft.com/en-gb/xbox/gdk/docs/features/com...
If I had a quid for every time I saw this comment on HN or Reddit I would probably be as wealthy as Gates himself. It is always an instant downvote for me, because they make me lose faith that people on HN have actually understood what a kernel is and how it works, and what ABI compatibility is, and what user-mode stability is. It is dogmatic and pointless.
The NT kernel is pretty good. Windows is generally well-architected. The NT kernel is the best thing about Windows, and you lot want to swap it out with something decidedly inferior.
Windows' user-mode applications and libraries are also pretty good. By user-mode apps and libraries I mean Win32 itself, WinRT, D2D/DirectWrite, D3D, Winsock, Windows Sound, and the thousands of entrypoints and enums for cool Windows stuff like the registry, synchronisation primitives, file management, special user files, cloud files, accessibility and internationalisation, and more. I've mentioned some other nice platform APIs in a sibling comment.
It is pretty easy to write a full-fledged GUI application on and for Windows that handles heavy use of networking, sound, graphics acceleration, etc without ever having to use a single third-party library, and make it run on OSs that are nearly 18 years old (not the case on most competition OSs).
I also daresay that IE/Edge moving to Chromium was in some ways a bad idea, as Chromium has become the de facto default Web platform, and any non-Chromium browser (Safari, Firefox) is likewise de facto non-conforming.
I disagree. .NET is fundamental to the Windows platform. It's like having a Python runtime installed by default in some Linux distros, which makes sense for that distribution's use-case.
Not quite sure about this. .NET is a superb platform, easy to write reasonably good code, huge standard library, well-maintained, many languages supporting a wide variety of paradigms (C#, VB, F#, PowerShell, C++). .NET is one of Microsoft's success stories.
In general, if you wanted...
Reliability: Japanese. Value: Korean, French, Japanese. Performance: German, Italian, maybe every now and then British. Luxury: German, Italian, British, and depending on marque, Japanese.
And today, Chinese marques are eating everyone's lunch on every metric in the EV sector because they have seen how everyone else builds cars, lorries, and buses for a while, learnt how to do it themselves, got rid of the ICE, popped a battery in them, and have been massively undercutting the market for a while now.
* I should qualify this properly to pre-emptively stave off the ooh-rah crowd: every now and then there has been a decent A-to-B car out of the US, like the Fiesta. Additionally there are models sold purely in Europe like the Ford Mondeo.
> to get a NEW ISO which you then install
This is not good.
Use an autounattend.xml, the mass graves, and a WinGet JSON to customise an online image.
[1]: https://schneegans.de/windows/unattend-generator/
[2]: https://learn.microsoft.com/en-gb/windows/package-manager/wi...
1. Right-click on an existing object, offer drop-down context menu.
2. Menu item `Position relative to...`.
3. The cursor now selects _other_ objects in the field.
a. If there is no other object, then offer to create a new label-less node with (x,y); default to the origin.
b. Once an object is selected, then offer `right of`, `left of`, `north of`, `south of`, `southeast of`, etc as a drop-down menu, and a field for radial displacement.
i. As a stretch goal, offer a `Custom position...` button to specify an (x, y) displacement, or a polar angle and radial displacement. These three options (fixed offsets, Cartesian, polar) could also be tabs in the resultant menu from (b) above.
You could use this same UI/UX for `anchor`, too.It's all still there. Bring it back, Microsoft. And put HiDPI and all your other modern technologies like D3D12 and borderless full-screen on it. I want to write old-school Win32 applications that fly.
What about these particular workloads (and the environments they're used in) make them 'serious' and why are other workloads 'lesser' and therefore the standard library 'suffices'? Why not use better containers for everything? Google, for instance, universally recommends Abseil.
Why is only 'high throughput, low frequency, massively concurrent work' considered 'serious'?
This is essentially what Vulkan does; there's a CreateInfo struct for every object creation or command function. And even then they managed to sort of mess it up, because they also have functions and objects suffixed with a '2', and the pNext extension mechanism.
Will never happen on Windows, especially not in user-mode libraries, and especially not something this pervasive.
Sadly the MSVC ABI makes std::span and std::string_view a pessimisation:
> BTW: As a nice addition, if you use SAL annotations
> Windows C++ Programming
Not everyone will see the irony, but the Windows user-mode application and library suite and the kernel now very heavily rely on the safety mechanisms of C++ that the author calls 'complex', 'uglif[ied]', and has 'los[t] the taste for good readable code'. I'm of course referring to the Windows Implementation Library: https://github.com/microsoft/wil This is explicitly an effort from MS WinDev to make Windows C++ code safer. User-mode applications writing native Windows code can and absolutely should use it, too.
Any time I see `void*` in C++ I ring-fence it as a C-ism and make sure I `reinterpret_cast`. For me, a bag of bytes is `std::span<std::byte>`. void* is a memory location with no provenance, no ownership, no size information, nothing. Do I even know if it is this program's memory, or some shared memory construct, or maybe even a pointer into GPU memory? No for all.
C likes to play fast and loose and its proponents call it 'beautiful and simple', I call it a segfault/use-after-free/double-free waiting to happen.