I used it recently to write a useful utility related to OpenTelemetry file processing. .NET AOT produced a single-file static binary which is similar in size to what Go would produce, and can be dropped into any target system and run without dependencies, just like Go does.
Yuck. I like both Go and C# a lot, and use them both professionally.
In my experience the strengths of Go are mostly
- Deployability via single-file static binaries
- Simple syntax that anyone can learn (no exceptions, no classes or inheritance)
- Wicked fast compile times
And the strengths of C# are
- Powerful language with null-safety and lots of syntax sugar
- Runtime-level coroutines so you don't need `async/await` everywhere
G# seems like it has the _worst_ of both worlds, not the best. It's fun to write compilers, and good on them for doing it, but no thank you for real use
It's a solved problem. The physics is simply such that it's really inefficient.
> ... we'd need a system 12.5 times bigger, i.e., roughly 531 square metres, or about 2.6 times the size of the relevant solar array. This is now going to be a very large satellite, dwarfing the ISS in area, all for the equivalent of three standard server racks on Earth.
The gist of it is that about 99% of cooling on earth works by cold air molecules (or water) bumping into hot ones, and transferring heat. There's no air in space, so you need a radiator 99x larger than you would down here. That adds up real fast.
Yes, slack is intermittently down for me and the rest of my company. It's intermittently losing messages, failing to load new ones, and showing error pages :-(
Now you understand why this app costs more than 2x the price of alternatives such as diskDedupe.
Any halfway-competent developer can write some code that does a SHA256 hash of all your files and uses the Apple filesystem API's to replace duplicates with shared-clones. I know swift, I could probably do it in an hour or two. Should you trust my bodgy quick script? Heck no.
The author - John Siracusa - has been a professional programmer for decades and is an exceedingly meticulous kind of person. I've been listening to the ATP podcast where they've talked about it, and the app has undergone an absolute ton of testing. Look at the guardrails on the FAQ page https://hypercritical.co/hyperspace/ for an example of some of the extra steps the app takes to keep things safe. Plus you can review all the proposed file changes before you touch anything.
You're not paying for the functionality, but rather the care and safety that goes around it. Personally, I would trust this app over just about any other on the mac.
I can't find a specific EULA or disclaimer for the Hyperspace app, but given that the EULA's for major things like Microsoft Office basically say "we offer you no warranty or recourse no matter what this software does" I would hardly expect an indie app to offer anything like that
Yep. At a previous job we had a file server that we published Windows build output to.
There were about 1000 copies of the same pre-requisite .NET and VC++ runtimes (each build had one) and we only paid for the cost of storing it once. It was great.
It is worth pointing out though, that on Windows Server this deduplication is a background process; When new duplicate files are created, they genuinely are duplicates and take up extra space, but once in a while the background process comes along and "reclaims" them, much like the Hyperspace app here does.
Because of this (the background sweep process is expensive), it doesn't run all the time and you have to tell it which directories to scan.
If you want "real" de-duplication, where a duplicate file will never get written in the first place, then you need something like ZFS
> This is basically only a win on macOS, and only because Apple charges through the nose for disk space
You do realize that this software is only available on macOS, and only works because of Apple's APFS filesystem? You're essentially complaining that medicine is only a win for people who are sick.
He "only" saved 30%? That's amazing. I really doubt most people are going to get anywhere near that.
When I run it on my home folder (Roughly 500GB of data) I find 124 MB of duplicated files.
At this stage I'd like it to tell me what those files are - The dupes are probably dumb ones that I can simply go delete by hand, but I can understand why he'd want people to pay up first, as by simply telling me what the dupes are he's proved the app's value :-)
In order to check if a file is a duplicate of another, you need to check it against _every other possible file_. You need some kind of "lookup key".
If we took the first 1024 bytes of each file as the lookup key, then our key size would be 1024 bytes. If you have 1 million files on your disk, then that's 128MB of ram just to store all the keys. That's not a big deal these days, but it's also annoying if you have a bunch of files that all start with the same 1024 bytes -- e.g. perhaps all the photoshop documents start with the same header. You'd need a 2-stage comparison, where you first match the key (1024 bytes) and then do a full comparison to see if it really matches.
Far more efficient - and less work - If you just use a SHA256 of the file's contents. That gets you a much smaller 32 byte key, and you don't need to bother with 2-stage comparisons.
I don't know exactly what Siracusa is doing here, but I can take an educated guess:
For each candidate file, you need some "key" that you can use to check if another candidate file is the same. There can be millions of files so the key needs to be small and quick to generate, but at the same time we don't want any false positives.
The obvious answer today is a SHA256 hash of the file's contents; It's very fast, not too large (32 bytes) and the odds of a false positive/collision are low enough that the world will end before you ever encounter one. SHA256 is the de-facto standard for this kind of thing and I'd be very surprised if he'd done anything else.
In iOS 17.4 Apple allows you to apply to create an alternative store. Apple can still deny your request and kill your alternative store, and this is exactly what happened.
Epic opened a developer account under their european subsidiary company, which applied for this, and Apple just banned that account, so Epic can't create a store. Perhaps if someone else (Google, Microsoft, Meta) made a store, Epic might be able to upload apps to that store, but because in the Apple world everything traces back to the developer accounts, I'm pretty sure that would be blocked by Apple as well.
As much as it might seem like Tim Sweeney was exaggerating about Apple's DMA "compliance" changes being hot garbage, a horror show, and malicious compliance -- he really wasn't. Apple are in full on villain mode here.
The part that doesn't make sense, is why Apple are choosing to be such dicks about everything, when the EU is already breathing down their necks. They're inviting more and harsher regulation upon themselves and making the rest of the world hate them in the process.
It looks like to use this product, I have to learn an entirely new programming language (which appears to be a weird mashup of Python and Haskell), a whole set of entirely new API's, I can only host my stuff on their for-pay cloud infrastructure, and I can't use source control?
That's a lot of very high hurdles to clear. Even if this magically solved all my scaling and distributed system problems forever, I'm not sure it'd be worth it. Good luck to them though for being ambitious.
That answer is only there because it's really old, from the early days of S.O. where people were allowed to ask questions that weren't super serious binary yes/no style. It'd get moderated and deleted in a heartbeat today. A forlorn monument to the cool place that S.O. once was
I've owned personally, and used macs for work since around 2009. I've never installed any third party window-snapping or management systems, and I don't consider it a big deal.
I do use window snapping on Win10/11 periodically, but TBH I find that the beefed up snapping in Win11 is more annoying than it is useful, often snapping things to quarters of the screen when I just wanted to move a window.
Likewise, I've seen non-programmer users on win10 hit the window snapping by accident and be confused and put off by it.
Would I like it if Apple were to build a power-user window snapping feature into macOS? Yes, I would. Am I upset at them for not including it? Certainly not. Were I a product manager for macOS I would find it hard to justify the investment, given all the other things they can and do work on.
There's a ton of apps now which require iOS15, and some are starting to move to 16. If you're stuck on 14 for jailbreak reasons I suspect you're going to struggle with more things than Wavelength.
It was nice. Feel free to take a look
https://github.com/OctopusDeploy/OtelImporter