• 0 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: September 24th, 2023

help-circle



  • I wish they’d fix some basic things like allowing apps to use ports under 1024, show setting the Bluetooth connection timeout, allow out of band Bluetooth pairing, some kind of working automatic file sync between my phone and PC, etc.

    Seems like they have run out of ideas and are just doing random stuff that nobody asked for now, or even things that are actively harmful to users (allowing apps to know if they are being recorded).



  • Those days never existed. Even the first iPhones were like $500 and that was over a decade ago.

    These prices are very high but phones last a lot longer than they used to and are improving a lot slower. I just bought a Pixel 8 for £400 which (accounting for inflation) is about the same price as we used to pay for three old Pixels and even Nexuses.

    E.g. the Nexus 4 which was considered “mega cheap” was £279 for the 16GB model, which is £390 in today’s money.

    They’re clearly going for price differentiation based on the model year, but you really don’t need the latest model to have an amazing phone any more.







  • Yeah I think it’s trauma due to C/C++'s awful warning system, where you need a gazillion warnings for all the flaws in the language but because there are a gazillion of them and some are quite noisy and false positives prone, it’s extremely common to ignore them. Even worse, even the deadly no-brainer ones (e.g. not returning something from a function that says it will) tend to be off by default, which means it is common to release code that triggers some warnings.

    Finally C/C++ doesn’t have a good packaging story so you’ll pretty much always see warnings from third party code in your compilations, leading you to ignore warnings even more.

    Based on that, it’s very easy to see why the Go people said “no warnings!”. An unused variable should definitely be at least a warning so they have no choice but to make it an error.

    I think Rust has proven that it was the wrong decision though. When you have proper packaging support (as Go does), it’s trivial to suppress warnings in third party code, and so people don’t ignore warnings. Also it’s a modern language so you don’t need to warn for the mistakes the language made (like case fall through, octal literals) because hopefully you didn’t make any (or at least as many).