- > I think this is incorrect. Specifically the Windows ARM support. Official hardware support page indicates that the Windows version requires x64. I unfortunately don’t have the hardware to confirm for myself. But Blizzard is the kind of company that would have made a blog post about that.
It has been around for a while, circa 2021. They made a forum post when they released it.
For reasons unknown the link no longer works but here it is on the wayback machine. https://web.archive.org/web/20210512205620/https://us.forums...
- > There's something to be said for the restrictions of an environment when you're learning how to operate in a domain that seems to shape future thinking.
When at University the academic running the programming language course was adamant the Sapir–Whorf hypothesis applied to programming language. ie language influences the way you think.
- To those who haven't heard how colossal the size of OpenAIs contracts are.
900,000 wafers monthly. Tom's hardware estimates that is equal to 40% of global dram production capacity.
https://www.tomshardware.com/pc-components/dram/openais-star...
- Didn't Microsoft drop 16 bit application support in Windows 10? I remember being saddened by my exe of Jezzball I've carried from machine to machine no longer working.
- This is an aside. Yesterday I was in a shopping centre (ie a mall) and a bunch of kids ran through the food court, maybe 10 of them all around the 9-12
A grumpy lady shouted at them "kids you shouldnt be running!"
I turned to whom I was eating with and our discussion could be summarised as "kids should be running. The problem isn't they're running, the problem isn't even directly where they're running. Where they're running is a symptom of them having no where else to run"
- You joke. I still use an old winamp 2.81 on my windows machine.
About 15 years ago I came across some plugin dll files that added flac support.
The only issue I ever run into is some non ascii characters in ID3 tags make that file unplayable. But winamp is perfectly capable of editing them.
It's even pretty good in the high dpi monitors because Ctrl-D enables "Double size" mode on the main window and equaliser. And the playlist window has customisable font sizes.
- It all depends on how the flow is implemented.
If it's a one time unlock, eg like developer mode then hopefully it'll just work.
If it's a big long flow per install... Yikes, that's not much better than adb install
- That's similar to me, I started using FreeNAS back in the 9.x days.
At the time the FreeNAS documentation recommend installing to a usb drive. This proved unreliable, but dedicating a drive to it was silly given it couldn't be used for anything else. I had all the things I needed but I wanted to peel back the layers and this seemed like a good excuse
So I threw in a drive and installed freebsd 10 and spent a few days familiarising myself with everything, learned how to configure samba myself, learned how to setup jails with iocage (the old shell version), and finally imported my pool.
Years later very little has changed.
- Interesting, that's been the opposite of my experience.
My Mum converted her homes down lights to LEDs over a decade ago. Hasn't lost a single one.
I moved into my current house 5 years ago, haven't lost a single one either.
- > Stalwart is essentially the first server implementation of JMAP
Just to clarify. Stalwart is the first to have JMAP contacts and calendars. Cyrus has had JMAP mail since the beginning of JMAP.
- Funnily enough, one of the things we were recommended was a pack of mini nut butter jars. Made specifically for the purpose of being a easy way to expose little ones to a variety of nuts before they could eat the nuts themselves.
Then at each meal put a tiny amount on a spoon and give to the little one before feeding the actual meal, and each meal use the next one butter.
It was great. Sure I can buy peanut butter, or maybe cashew at a grocery store. But I've never seen pecan butter, Brazil nut butter etc.
- Hi,there's a lot to unpack here.
> They could always move to a compatible license? > No, it was always designed to be hostile to Linux from the outset. It's a project that doesn't want to interoperability with Linux
I'm not sure why you've jumped here. I didn't mention a specific project or licence.
But, nonetheless I'm going to assume you mean OpenZFS.
1. No they can't change the license. Much like Linux contributors retain their own copyright, OpenZFS can't just change the license. The only group that could hypothetically change it is Oracle given the clause the steward of the license can release a new version, but that's unlikely and Oracle has absolute nothing to do with the existing project.
2. Staying on the license and compatibility. It's really quite confusing on what's compatible in the eyes of Linux. The very fact they have separate export and export GPL symbols suggest Linux as a project sanctions non GPL modules, and considers them compatible if they only use those symbols, perhaps in the same vein as they consider the syscall boundary to be the compatible with non GPL? If someone who is actually in the know about why there are two sets of exports if love to be know.
3. Always designed to be hostile to Linux. Whether that's true or not is the debateable, there are conflicting opinions from those who worked at Sun at the time. Also the comment criticises a community that had no hand in whether or not it was intended to be hostile to Linux or not. In the end is copyleft software, very similar in spirit to the Mozilla public license. And by definition copyleft licenses are inherently incompatible without specific get out of the jail clauses to combine them (see MPLv2 for example).
4. Re interoperability. Strongly disagree. OpenZFS takes great strides to be compatible with Linux. Each release a developer sends hours pouring over Linux changes and updating a compat layer, and the module remains compatible to compile against multiple Linux versions at any one time, there are even compat patches to detect distro specific backports that while the version hasn't changed the distro have back ported things that change behaviour. That's a serious commitment to interoperability. And a large number of openzfs devs do their work against Linux as their primary platform, hence why the FreeBSD rebased their ZFS upstream on ZFS on Linux, leading it to become the official upstream OpenZFS. I can't see how anyone could say in good faith they don't care about Linux compatibility unless they haven't looked over at the openzfs project for over a decade.
4. Re why do I think Linux folks should maintain APIs for them.
The way you worded this strongly implies I was saying Linux should maintain an API for them. In no way did I say that. I was replying to a post that was adament that Linux doesn't remove things. I provided a perspective that Linux does in fact remove things. I wasn't arguing for maintaining any API, Linux doesn't even guarantee internal APIs for themselves. I was pointing out changing a symbol export from export to everyone to export GPL only isn't changing it, given it's the exact same API they've just simply removed it for some groups.
None the less I think it'd be great if Linux could maintain some APIs for out of tree modules. But they don't and that's fine. I just find changing exports from open for everyone tomorrow GPL only to be rather hostile.
Really, no one in either of these communities had any say in their license (sans Torvalds). Both creating great stuff for we as users to run. And it'd be great if people working on free software could get along, and those in the peanut gallery didn't prescribe malcontent between them because of a difference in license they didn't pick.
- That's all a matter of perspective.
Is moving a symbol from EXPORT_SYMBOL(some_fun) to EXPORT_SYMBOL_GPL(some_func) actually changing the API? Nope, the API is exactly the same as it was before, it's just changed who is allowed to use it.
From the perspective of an out of tree module that isn't GPL you have removed stuff.
I'm honestly not sure how one outside the kernel community could construe that as not removing something.
- I can only speculate, but maybe they're referring to the same thing Andrew Morton meant when he described ZFS as a rampant layering violation.
ie ZFS isn't just a file system. It's a volume manager, raid and file system rolled into one holistic system vs for example LVM + MD + ext4.
And (again I'm only speculating) in their micro kernel design want to have individual components running separately to layer together a complete solution.
- > If it didn't actually work, it would've been discarded by companies long ago
That makes the assumption that company hiring practices are evidence based.
How many companies continue to use pseudo-science Myers Briggs style tests?
- Microsoft had a POSIX personality on NT since its release in 1993.
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
Then with the release of XP it was replaced with: https://en.wikipedia.org/wiki/Windows_Services_for_UNIX
- > WSL 1 was relatively innovative, integrating Linux application compatibility into the Windows operating system itself
Both FreeBSD and Illumos were running Linux applications (at various levels of compatibility) many years prior to wsl v1. Joyent even went as far as re-implementing the Docker api to allow running OCI images natively in LX zones. Hence, it wasn't even that novel of an idea.
- If I remember correctly you need both. Program the cells to be X organ cells, and provide a scaffold for them to grow on.
- I just restarted using RSS recently. And I discovered I can also use it to track software releases (on github). The url is the release page with .atom appended. Eg
- Two? I envy you.
I really wish I had the space for another CRT. One day I hope to have a second for two player time crisis.
- I've decided that titles are mostly meaningless in software. What X title means in one org means another in a different one with near zero overlap, and another title might have considerable overlap with a differently named one but viewed lowly, borderline pejoratively at another org. Eg system admin vs devops vs sre. In one org sysadmins are deploying desktop machines with no expectations they can cut code, in my old role as one I was working with Linux systems, building glue and orchestration, and when things go wrong debugging backend code written by a development team. Something far closer to the work of "devops" or "sre".
As a aside, I find your example of doctor as amusing because it's overloaded with many considering the term a synonym of physician, and the confusion that can cause with other types of doctors.
- Perl has subroutine signatures now. You can write
sub foo ($x, $y, $x) { ...}
It's just syntactic sugar, so you still can't pass in multiple lists, and the list must be the final parameter.
- Not sure if you've deliberately put in two bugs there haha
1. shift only shifts off the first element.
2. (if classify this as a bug) using $a and $b are frowned upon because they're the default variables when using sort.
- I visited Denmark a few years ago and went to the Hans Christian Anderson museum in his home town of Odense.
It's absolutely fantastic, the museum is presented like a story you walk through his life.
Highly recommend!
- I gave up and started buying $4 rshirts. Why? Because each year the clothes I'd buy were were on quality than my previous clothes.
When buying a $4 shirt I know the price:quality ratio, it's cheap:crap. Whereas majority of the time buying more expensive it might be slightly better, but it's still expensive:crap.
- I really enjoy the TV show Escape to the Chateau. A lot of couple buy an old run down French chateau and move in with their two kids. Each episode is roughly them doing up a part of it. Often with ideas for making money out of it.
Very much light entertainment, but it's eye opening how significant of a restoration and maintenance burden it is.
- `dir` was also in CP/M. Though it didn't have a concept of a file hierarchy, so it listed all files on the disk (but did support supplying a pattern to filter against).
- It'd be interesting to see open data about this.
My understanding is games with microtransactions optimise for "whales", people who spend inordinate amounts of money. While the majority of users don't pay anything, or at most very little.
- Yes! It's reusable, but not duplicated.
[1]https://metacpan.org/pod/App::Cronjob https://metacpan.org/dist/App-Cronjob/view/bin/cronjob