You mean there's two of us?
326 publicly visible posts • joined 10 Feb 2010
This is rich, considering the article is explaining how everything being a file (a POSIX concept which the main author of NT railed against on the record) prevented Optane from being really useful because it HAD to be a file and HAD to be handled as a filesystem (secondary storage).
You mean 75% of the Rust code being initializing and setting up the HAL environment so your logic can remain the same if you swap RP2040 boards? Not worth it in this case, since the logic is so small, but have a larger thing to do and you can port it by just swapping values on the "bloat" section.
Write well, write once.
Because although Microsoft is moving to the command-line, and supporting SSH administration of Windows Server, a good CLI text editor for modern Windows is 404 in the base install. Which means I usually have to resort to gvim; and I've tried everything:
- YEDIT: not a real installer, not a self-contained executable, and not signed. The same author wrote what is by far the best alternative to CMD.EXE (YORI).
- Open Watcom VI: still exists in GitHub, unbundled from OpenWacom, but doesn't support UTF-8
- Kinesics Text Editor: needs Admin permissions to install, no UTF-8
- FTE: needs very old MSVC libraries
- Thomson-Davies Editor: no UTF-8
- Micro: Go port of Nano - but that's Nano, not CUA
>checks Tilde website
>no Windows binary
You mean Microsoft's equivalent to Apple's HFS Resource Forks? From 1985?
It's amazing, a company tries to support advanced functionality and because everyone else can only think in flat files the advanced functionality is a mistake.
It's like UNIX "everything's a stream so just hack at the bytes" vs NT "everything's an object and you should use methods to handle them" - idiots try to hack at NT objects because that's the lowest effort option and get surprised when they blow up in their face, so that's *obviously* Microsoft's mistake.
Linux devs don't have to wonder; unless they keep up to date with the dependencies, their programs break with the next version of each distro. There was a time where you couldn't compile Samba from source on RHEL7 because of a missing library that had been marked as "deprecated" and "WONTFIX" by Red Hat. Samba!
No it isn't [/Cleese]
There must be something missing with your .conf, whenever I edited my resolv.conf the change was immediate.
In fact, for all the gnashing of teeth about systemd, base Debian netinstall is free of NetworkManager and Systemd-resolved out of the box, you have to go out of your way to activate them.
Of course, if you pile up "Desktop" and "GNOME" (phear!) in tasksel, all that cr*p starts to come to the surface...
OCP hardware is so different from anything else in a datacenter and needs so much specialty support that it only makes sense if you're deploying several rows of racks or you have a greenfield deployment; if you have just two or three racks it doesn't make sense, and Inspur won't return your calls anyway.
Mob rule is amazing. It's opt-in. It has been clearly stated and disclosed. Compared to Microsoft, Muse Group has been a model citizen. If you're worried about being silently activated after you opted-out, do you audit the source code of each and every patch you apply? Well, you should then. Might find that's all you do, and unless you're being paid to do just that, you won't get anything else done. Enjoy your bugs. Fix them yourselves, it's open source! Fork Audacity. Fork it from orbit. It's the only way to make sure.
Even a pop-up offering to send a report after a bug doesn't catch many categories of bugs, and most people hit Cancel on those anyway.
About the Google and Yandex integrations, they leave me uncomfortable, but should Audacity, which survives on contributions, spend contribution money creating an analytics platform?
Where's the open source and free as in freedom analytics platform with a worldwide CDN, guys? Isn't open source the solution to all problems?
That 70% percentage I quoted of vulnerabilities because of memory/data-race/side-effect? Microsoft et al. That's why they are firefighting it right now with Rust and have sponsored the Rust Foundation while developing an in-house equivalent codenamed Verona.
Apple is working on a Rusty Swift and although Google went to the trouble of hiring the best minds in language development to create Golang, they're still using Rust inside the Fuchsia kernel.
Look around. You may think all that software was reliable but how stringently was it tested, really? Did you have fuzzers back in the day like we have now? If you need to recompile it today, how much of its behaviour was defined by the choices of the previous compiler about what to do on the several places where a language has "undefined behaviour"?
Rust (or any similar language) can't help with errors in code logic. But it definitely helps with 70% of existing errors, which are of the memory/data-race/side-effect variety and that usually can't be caught in development, only in production. Rust ensures, at least, that if it compiles, it's mostly free from those.
Cue everyone complaining that Rust is hard and the compiler is slow...
Several forests have been decimated to produce MITRE code standards, but nobody follows them (Minimal Viable Product is the law of the land, security be damned) and even following them to the letter, C and derivatives should be classified "Unsafe at any speed", even (or especially) legacy code. Rip it all up and start again with GC/RefCount/RAII languages.
Nuke it from orbit, it's the only way to make sure.
PowerShell demands a different way of thinking, and since Windows is based on API calls and not on text files something "shell-y" like cmd or even bash would never work. Unless you want to go back to VBscript syntax as a shell. Do you? I don't.
I'm finding it very *discoverable*.
PS> Get-Something --> receive objects, objects have properties and properties have values
Want to see only some properties?
PS> Get-Something | Select Property1, property 2 ! Format-Table
Want to filter by value?
PS> Get-Something | Where Property -eq(*) value
(*) almost the same comparators as bash test
Found what you want to change?
PS> Set-Something -Name thingamajig -Property pants -Value leather -Enabled
It's not much different than using sed and awk to filter data until you get information. You just have to know how to look for what you need, instead of memorizing netsh, net, netdom, and all the other stuff. Because cmd, without those other utils, is hopeless. And those utils still work in PowerShell, for now.
Every time I complained about sites not following standards and breaking Opera 12, all I heard, especially from the Firefox crowd was, "git gud, no-one cares about a browser with single digit market share". And when Opera complained about it to the EU, it was "sore losers, can't win in the market".
The only thing preventing me from exploding in schadenfreude is that I don't want Firefox to be left for roadkill. Monocultures are bad, even when they're from "cool" Apple or "nerd" Google and not "evil" Microsoft.
There used to be something called the ITU, that had lots and lots of technical documents and specifications about communication protocols, but then geeks took over and started swapping RFCs. Geeks start with the best intentions but totally fail to see the big (political) picture: cf. Facebook, fake news, and the death of journalism.
I'm on the Slow Ring and for the last two flights, I only start getting preview builds less than two months before release... There used to be an initial build two months after release of the previous version, one pre Bug Bash, one post Bug Bash, and one near release.
The link to the Frederic Vachon presentation is the german-dubbed one. It all sounds like a killer joke to me.
If you go to the official link https://media.ccc.de/v/35c3-9561-first_sednit_uefi_rootkit_unveiled , you can choose between audio versions and listen to the original audio on CCC's video player .