My point is that in a good code base types should be obvious from context. If you don't know the context then you will be slow (and make a lot of mistakes) no matter what the type say because you'll likely misunderstand…
Pointless typing and verbose code has nothing to do with writing code - it's all about code being readable. Java type declarations can be 20+ characers - just scanning through the code and having to skip all that junk…
I'm not saying Java should have introduced ground breaking features - I'm saying they made design mistakes that they should have corrected far sooner (var/type inference) and refused to add some basic features (lambdas)…
Not really - Java designers were just plain wrong and it took forever to admit it - things like local type inference (var) made the language pointlessly verbose for ages, and simple features like lambdas made the…
When you add those to the mix you're dealing with destructors, ownership, etc. so I don't see anything wrong with using stuff like unique_ptr/shared_ptr. And C tends to reinvent object oriented programming with each…
>The Java strategy of being very conservative about what you add to the frontend would have done C++ a lot of good after C++11 (or even before that). Java lost a lot of mindshare to C# and Kotlin due to that "strategy".
I'd guess there is there is too much money in it due to the fact that central banks killed interest rates and started buying government bonds as needed - where pension funds would hold those they now need to search…
> and someone brings up the fact that ISIS used one of them... They used Facebook, Twitter and YT for propaganda and Gmail for coordination (that thing about saving a mail draft on gmail instead of sending it), it's…
>Yes, it gains you some of the economics of factory construction and that you can start small and scale a location, but on the other side you lose that again because you lose the economics of scale that traditional PWR…
Thing is this kind of design benefits massively from economies of scale, same kind of thing that has drawn the price of PV down and other green energy.
> I am really stoked for the future of programming languages, when localization is just a matter of translating some words. My experience with localised codebases (in my native language) have been horrifying - like it…
You make a good point ! The thing I would put on communism is reduction of wealth and standards, so when the west rebuilt and went forward we got stuck with concrete slabs. It's just shocking to me how the architecture…
True, I'm just not sure that I'd trust the DB isolation once the user has SQL injection. I never saw a SQL injection report on a project (well since the PHP days) ORMs solved this for the most part, but I did see…
Well if you have SQL injection bugs then you have bigger issues to worry about - I've used this to enforce multi-tenancy on database access level (like another poster said - preventing queries accessing wrong data by…
>That makes connection pooling difficult and presents its own security issues on limiting the tenant to only their DB user. Can you use SET LOCAL ROLE <user> on each transaction ?
My uneducated gut feeling is that the only way nuclear is going to be relevant is if they perfect micro-nuclear reactors. I remember reading about these 10 years ago [1], and have seen a few more since. Basically they…
That's kind bad - first of all 50$ can be really low depending on the region, but more importantly this disregards the time spend on looking for exploits that don't pan out. So I would multiply that 50$ by at least 4.…
> it's such a huge improvement I can't imagine going back In what way ?
I find it funny that anyone would romanticises socialist architecture. I've grown up in a port town in former Yugoslavia (Rijeka) and if you walk throughout the city it's obvious the communist revolution was a…
That's not much of a value gain it would just push the industry further away from ARM. x86 has a lot of legacy power and it enjoyed being the only relevant platform for a long time in a lot of markets so there's a lot…
>That said, no matter which way you skin it, if you increase complexity then you increase risk. This isn't really true, for eg. if you add redundancy technically you increase the complexity but also reduce risk (point…
I don't know enough about Excel but I highly doubt it's about the looks - I have Office installed on my MBP and the ribbon looks like I remember it from Windows. I don't understand your point - non-native widgets are…
> a false sense of security You mean placebo effect ?
The store should set it's policy, law just ensures equal rights and review process for developers
They did a decent job with credit cards eventually. Developers leaving won't happen, Apple and Google will cut a deal with big guys (Netflix, Amazon) and ignore smaller players (even Epic in this case)
My point is that in a good code base types should be obvious from context. If you don't know the context then you will be slow (and make a lot of mistakes) no matter what the type say because you'll likely misunderstand…
Pointless typing and verbose code has nothing to do with writing code - it's all about code being readable. Java type declarations can be 20+ characers - just scanning through the code and having to skip all that junk…
I'm not saying Java should have introduced ground breaking features - I'm saying they made design mistakes that they should have corrected far sooner (var/type inference) and refused to add some basic features (lambdas)…
Not really - Java designers were just plain wrong and it took forever to admit it - things like local type inference (var) made the language pointlessly verbose for ages, and simple features like lambdas made the…
When you add those to the mix you're dealing with destructors, ownership, etc. so I don't see anything wrong with using stuff like unique_ptr/shared_ptr. And C tends to reinvent object oriented programming with each…
>The Java strategy of being very conservative about what you add to the frontend would have done C++ a lot of good after C++11 (or even before that). Java lost a lot of mindshare to C# and Kotlin due to that "strategy".
I'd guess there is there is too much money in it due to the fact that central banks killed interest rates and started buying government bonds as needed - where pension funds would hold those they now need to search…
> and someone brings up the fact that ISIS used one of them... They used Facebook, Twitter and YT for propaganda and Gmail for coordination (that thing about saving a mail draft on gmail instead of sending it), it's…
>Yes, it gains you some of the economics of factory construction and that you can start small and scale a location, but on the other side you lose that again because you lose the economics of scale that traditional PWR…
Thing is this kind of design benefits massively from economies of scale, same kind of thing that has drawn the price of PV down and other green energy.
> I am really stoked for the future of programming languages, when localization is just a matter of translating some words. My experience with localised codebases (in my native language) have been horrifying - like it…
You make a good point ! The thing I would put on communism is reduction of wealth and standards, so when the west rebuilt and went forward we got stuck with concrete slabs. It's just shocking to me how the architecture…
True, I'm just not sure that I'd trust the DB isolation once the user has SQL injection. I never saw a SQL injection report on a project (well since the PHP days) ORMs solved this for the most part, but I did see…
Well if you have SQL injection bugs then you have bigger issues to worry about - I've used this to enforce multi-tenancy on database access level (like another poster said - preventing queries accessing wrong data by…
>That makes connection pooling difficult and presents its own security issues on limiting the tenant to only their DB user. Can you use SET LOCAL ROLE <user> on each transaction ?
My uneducated gut feeling is that the only way nuclear is going to be relevant is if they perfect micro-nuclear reactors. I remember reading about these 10 years ago [1], and have seen a few more since. Basically they…
That's kind bad - first of all 50$ can be really low depending on the region, but more importantly this disregards the time spend on looking for exploits that don't pan out. So I would multiply that 50$ by at least 4.…
> it's such a huge improvement I can't imagine going back In what way ?
I find it funny that anyone would romanticises socialist architecture. I've grown up in a port town in former Yugoslavia (Rijeka) and if you walk throughout the city it's obvious the communist revolution was a…
That's not much of a value gain it would just push the industry further away from ARM. x86 has a lot of legacy power and it enjoyed being the only relevant platform for a long time in a lot of markets so there's a lot…
>That said, no matter which way you skin it, if you increase complexity then you increase risk. This isn't really true, for eg. if you add redundancy technically you increase the complexity but also reduce risk (point…
I don't know enough about Excel but I highly doubt it's about the looks - I have Office installed on my MBP and the ribbon looks like I remember it from Windows. I don't understand your point - non-native widgets are…
> a false sense of security You mean placebo effect ?
The store should set it's policy, law just ensures equal rights and review process for developers
They did a decent job with credit cards eventually. Developers leaving won't happen, Apple and Google will cut a deal with big guys (Netflix, Amazon) and ignore smaller players (even Epic in this case)