> I'm surprised how few competitors there are in the Dropbox space.
There used to be many more - Sugarsync, AeroFS, Syncplicity, just to name a few - all bit the dust. Box.com found a niche serving business document flows; Gdrive, iCloud, OneDrive, all survived thanks to being features in a broader Big Tech suite. Everybody else? Outcompeted, plain and simple. Dropbox was just a cut above.
(I used to work at one of the companies named above, so although it's just one person's opinion, it's at least as informed as anyone else's here :) )
Right! Naturally, our Congress is full of technical and administrative expertise and totally has the time, patience, and will to cleanly and carefully craft the wide body of regulation we've grown to require for a smooth and healthy and productive society. No reason for those awful technocrats to usurp such authority when we've got a capable and knowledgable legislative branch capable of doing the work just as well.
Gotcha, I must have encountered them later on then - thanks for posting the receipts!
I was a happy user for a while, but eventually some bugs drove me back to iTerm2 (in my case, hanging forever after certain terraform commands finished). Ghostty has filled my need for a better terminal since then.
Warp was always an AI thing, as I recall - the seem much heavier on AI bandwagon nowadays, but their whole thing was a terminal for teams where you could share knowledge and command palettes and generate stuff.
The semantics are very relevant, since you presented it as a supply-chain attack. If you call a library vulnerability a supply-chain attack, then your argument has lost coherence.
> The OC is somehow under the illusion...
Avoiding package managers with shitty policies is the silver bullet for this attack vector. I get that it can be useful in the moment to retract published artifacts, or update them in-place, or run some code after your artifact is downloaded, but all of these are false economies in our hostile environment.
Log4Shell was hardly a supply-chain attack - just a latent bug in a widely-used library. That can happen anywhere.
Maven to this day represents my ideal of package distribution. Immutable versions save so much trouble and I really don't understand why, in the age of left-pad, other people looked at that and said, "nah, I'm good with this."
I don't see the incongruity. It's one thing to mandate that retailers not sell alcohol to children, but it's quite another to require that all computers must report on the identities of their users just so that children don't see porn. The proper analogy would be require verification on the part of the porn sellers.
> while ignoring the fact that these laws provide tools allowing parents to do just that
These tools are called "parental controls" and already exist - we don't need laws to compel their production.
...unless, of course, the true aim is to use this as a beachhead for further expansion of privacy-violating requirements.
You write this off as a "slippery-slope" argument, but given that there are already quite a few tools that do what this law aims for, what's the point?
Reminds me of the story of one of my favorite pieces of classical music, 'Scarbo' by Maurice Ravel. It's one of the most technically difficult pieces played today. Ravel wrote it because he 'wanted to make a caricature of romanticism. Perhaps it got the better of me.'.
Maybe I'm wrong about the state of Java in Android today - it's been a few years since I did that work full-time. But I do remember when Kotlin broke on to the scene in 2015, and most of us were thrilled to finally move beyond Java 7! The embrace of a non-Java language was grassroots and genuine; Google's adoption came several years later.
J++ though, now that is a blast from the past! I think I still have a J# book from my student days, somewhere :)
Android folks have good reason to have anti-Java bias. Their bias, as it happens, is against old Java, which they are constrained to use as fallout from the Oracle lawsuits of yore. Kotlin breathed new life into Android in a meaningful way.
On backend teams, I've not personally encountered much anti-JVM bias - people seem to love the platform, but not necessarily the language.
(yes I know there's desugaring that brings a little bit of contemporary Java to Android by compiling new constructs into older bytecode, but it's piecemeal and not a general solution)
complexity in software is invisibly-preceded with "unnecessary", and usually indicates software that is difficult to maintain or even to verify its behavior. A really cool software architecture can scratch a similar itch as a good fugue, but that's not its typical function nor is it the way we usually engage with software professionally.
Bach's complexity, incidentally, is seldom "for its own sake" - the pieces all fit together beautifully and without extraneous movement. Contrast that with some lesser works by later composers like Liszt, where you often get the sense that a given passage could be reduced or removed without harming the work.
Lol I "love" that the first benefit this company lists in their jobs page is "In-Office Culture". Do people actually believe that having to commute is a benefit?
Yep! A formative experience of my childhood was working out how to type SMTP commands over telnet and sending mail from [email protected] to my dad. Such "opportunities" vanished decades ago.
There used to be many more - Sugarsync, AeroFS, Syncplicity, just to name a few - all bit the dust. Box.com found a niche serving business document flows; Gdrive, iCloud, OneDrive, all survived thanks to being features in a broader Big Tech suite. Everybody else? Outcompeted, plain and simple. Dropbox was just a cut above.
(I used to work at one of the companies named above, so although it's just one person's opinion, it's at least as informed as anyone else's here :) )