cageface

42 ms·

631.
by cageface 5y ago
I normally refrain from making meta comments about site implementations but this site doesn't scroll at all in Safari. There needs to be a hippocratic oath of web development.
632.
by cageface 5y ago
I guess it depends on the language but I've definitely had problems with codebases that depended heavily on static initializers. IMO it's usually better to explicitly bootstrap your code.
633.
by cageface 5y ago
Isn’t a static class essentially just a namespace?
634.
by cageface 5y ago
The two biggest problems with OO as it's traditionally used are: 1. Implementation inheritance creates brittle, tightly coupled and difficult to test code. 2. Mutable classes force you to structure data updates in a particular, inflexi
635.
by cageface 5y ago
Some of the biggest messes I've had to clean up in my career were created by inexperienced people blindly following Uncle Bob's principles. Pragmatism should come before all else in software IMO.
636.
by cageface 5y ago
I prefer to use undefined over null since it just fits more naturally with other TS features like optional fields. But I agree with using tsc’s no implicit returns check.
637.
by cageface 5y ago
I really like Svelte and want to see it succeed but I think it's more likely that React will somehow adopt innovations from other frameworks and remain dominant. I'd love to be wrong about this. Especially since I'd rather no
638.
by cageface 5y ago
Also picking a name that can easily and unambiguously searched on is a big plus.
639.
by cageface 5y ago
Typescript, esbuild, and preact would have been described as shiny not very long ago. These things take time to mature. I agree that the current JS ecosystem is fine if you don't get too far off into the weeds with obscure dependencies
640.
by cageface 5y ago
I've seen some NoSQL object/schemaless database turn into intractable balls of mud over time. Things that would be trivial in a relational DB with joins can turn into major engineering efforts and data corruption can be very hard
641.
by cageface 5y ago
Prepared statements are a good tool to have in your arsenal but for the majority of the queries you need an ORM will be fine. It doesn't absolve you of the need to understand SQL but it does save a huge amount of time and generally res
642.
by cageface 5y ago
Building SQL queries by gluing strings together is tedious and error prone. So you write a lot of helper functions to build queries for you and pretty soon you've invented your own crappy ORM. Why not save a lot of time and bugs and us
643.
by cageface 5y ago
This isn’t necessarily to Facebook’s advantage. Everybody I know in Asia is all over TikTok now. They’re not deleting their FB accounts but they spend a lot less time there.
644.
by cageface 5y ago
Because Facebook's algorithms actively amplify negative and provocative information. They could choose not to do this and accept lower profits. If they had a purely linear chronological feed then a lot of these problems would vastly di
645.
by cageface 5y ago
They're not gatekeepers, they're amplifiers. You can still make your own website and post whatever you want. The problem is what the amplifiers are amplifying.
646.
by cageface 5y ago
A lot of statically typed languages leave array indexing as a loophole for convenience but yeah this can also be a source of errors.
647.
by cageface 5y ago
I have not found this to be the case in Typescript code I've worked on. The main issue I've found with TS is stuff coming in from outside the system as JSON that doesn't conform to expected formats.
648.
by cageface 5y ago
I did iOS dev for many years. When I switched from Obj-C to Swift almost all my runtime errors vanished because the compiler caught them for me. Now I consider nil safety as an essential feature of any modern language.
649.
by cageface 5y ago
I’ve found a lot of the elegance of hooks disappears when you start maintaining the dependency lists. It’s far to easy to introduce subtle bugs or huge performance regressions with innocent looking changes. Feels like we need a new language
650.
by cageface 5y ago
This article also says that another trial that were included in previous meta-analyses should probably also be excluded and once all that's it's unlikely the meta-analysis will show an effect: As these two papers1,6 were the only
651.
by cageface 5y ago
I thought the Great War by Peter Hart did a good job of telling the story of the rapid advances in weaponry and tactics over the course of the war. It's grim but fascinating reading. https://www.irishtimes.com/culture&#
652.
by cageface 5y ago
Of course Apple is going to play by the rules of the jurisdictions they want to sell their products in. That's why their reassurances that they would never bend to government pressure on their CSAM plans were so worthless.
653.
by cageface 5y ago
To an extent they do but they've refused to implement a lot of important features in iOS safari that are needed for fully capable PWAs.
654.
by cageface 5y ago
Cameras are one of the few areas where phones are still making regular advances. Otherwise a phone from 2-3 generations back will probably meet all your needs.
655.
by cageface 5y ago
The difference is Android gives you options. If you’re locked into iOS you’ve got no recourse if you disagree with Apple’s decisions.
656.
by cageface 5y ago
You don't like the 3rd? I'd put the Eroica in my top 10 list of symphonies by anybody.
657.
by cageface 5y ago
Yeah that's true but if you stick to the major labels and performers you're very unlikely to hear a performance that bad. IMO worrying too much about this as a beginner is a distraction. But once you start to develop some favorite
658.
by cageface 5y ago
If you think you might like opera check out the René Jacobs' recordings of Mozart's Italian Operas on the Harmonia Mundi label: Cosi Fan Tutte, Le Nozze di Figaro & Don Giovannni. In general as a beginner I wouldn't worry
659.
by cageface 5y ago
Delta wasn’t dominant by May. Does this still hold?
660.
by cageface 5y ago
iCloud is certainly not fully E2EE.

More ›