

Ah yeah no call recording is so stupid. It’s not even illegal in most of the world. There are plenty of phones that unofficially support it too and they have never got in legal trouble.
Ah yeah no call recording is so stupid. It’s not even illegal in most of the world. There are plenty of phones that unofficially support it too and they have never got in legal trouble.
Yeah that’s exactly it. Think how many web sites stupidly disable right click. App authors will do exactly the same except it will be even more annoying to work around.
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).
The fist iPhones weren’t flagships.
Lol what. Do you know what a flagship is?
brought nothing new
How old are you? This is very obviously complete nonsense to anyone who was around at the time.
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.
They clearly don’t care too much about that privacy leak or it would have taken them less than 13 years to fix it in the first place (yes really).
Yeah I kind of agree but I also think when it gets to that point we’ll have much bigger problems than programmers losing their jobs. Like, most of society losing their jobs.
Yeah… Usually if you join a company with bad practices it’s because the people who already work there don’t want to do things properly. They tend to not react well to the new guy telling them what they’re doing wrong.
Only really feasible if you’re the boss, or you have an unreasonable amount of patience.
No I’m good with smart IDEs. Anyway don’t people set up Vim as practically an IDE these days anyway? That’s what Vim users always tell me.
Yeah IIRC it deletes them, which is as mad as you would expect. Maybe they’ve fixed that since I used it last which was some years ago.
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).
Yeah most uses of the factory pattern are unnecessary and it’s mild code smell IMO. If your factory only returns one type you should definitely just use that type’s constructor.
This can work for junior devs who aren’t stuck in their ways. Unfortunately there are too many “senior” devs who are happy making crap. It’s hard to fight them constantly to do things properly (e.g. write actual commit messages rather than just “Fix #836”) so using tools like linters where possible is definitely a big improvement.
I liked Netbeans much more than Eclipse. It didn’t have that stupid workspace system at least.
If you consider that “pretty close” then I think you’re going to dismiss anything else I say as insignificant anyway.
You can’t have a full integrated debug session with a watch window, locals (with an expandable tree for objects), stack, breakpoint list all visible at once. I.e. something comparable to this.
They’re not significantly different. Maybe it takes you 1s and me 2s. Not worth the effort of learning. Especially because Vim comes with significant downsides compared to full IDEs that will make you slower overall.
you really think its a giant conspiracy from elitists lying about their experience
Pretty much, yes.
You think thousands of developers are handicapping themselves for bragging rights?
Absolutely. That’s completely normal human behaviour.
Line numbers are absolute, not relative (normally anyway; I think some editors allow showing relative line numbers). Anyway I think holding down (page) up/down is going to be just as fast.
Still waiting to be able to listen on ports less than 1024…