rubber_duck

6 ms·

1.
by rubber_duck 6y ago
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 the domain
2.
by rubber_duck 6y ago
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 makes my eyes mor
3.
by rubber_duck 6y ago
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) that
4.
by rubber_duck 6y ago
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 standard libraries terrible
5.
by rubber_duck 6y ago
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 library s
6.
by rubber_duck 6y ago
>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".
7.
by rubber_duck 6y ago
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 positivie returns an
8.
by rubber_duck 6y ago
> 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 obvious the oth
9.
by rubber_duck 6y ago
>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 gets. You mean the
10.
by rubber_duck 6y ago
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.
11.
by rubber_duck 6y ago
>As I said in another thread, the problem is not writing the SQL. The problem is everything else after you have written it (applying on deploy, automating for other's dev envs, rollback, etc) What's wrong with migration manager
12.
by rubber_duck 6y ago
IMO watching a few sci-fi movies in 4k+ looks ridiculous - I start noticing the difference between CGI environment and actors and it kills the immersion completely, it goes from "that character is really there" to "this guy i
13.
by rubber_duck 6y ago
> 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 or not terminology
14.
by rubber_duck 6y ago
>Simply, if a restaurant offers 20 different dishes, it means each dish gets 20x less attention than if you had only one choice. Less fresh ingredients, less time perfecting the recipe and preparation. Serving only one dish makes things
15.
by rubber_duck 6y ago
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 and aesthetics r
16.
by rubber_duck 6y ago
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 multiple instance
17.
by rubber_duck 6y ago
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 accident, which is
18.
by rubber_duck 6y ago
>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 ?
19.
by rubber_duck 6y ago
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 propose small "nu
20.
by rubber_duck 6y ago
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. But still li
21.
by rubber_duck 6y ago
Not really true - there are plenty of buildings for the common folk from say 1920-1950, large apartment complexes where your middle class people would live. They aren't grandiose but the level of attention to detail, design and fitting
22.
by rubber_duck 6y ago
> it's such a huge improvement I can't imagine going back In what way ?
23.
by rubber_duck 6y ago
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 regression in stand
24.
by rubber_duck 6y ago
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 of cost in m
25.
by rubber_duck 6y ago
>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 being complexi
26.
by rubber_duck 6y ago
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 not a de
27.
by rubber_duck 6y ago
Umm - a large group of most popular productivity apps are cross platform and look nothing like native - from dev tools like IDEA, VSCode over Slack, MS Office, to multimedia tools like Adobe tools, almost all 3D modeling software like maya,
28.
by rubber_duck 6y ago
> a false sense of security You mean placebo effect ?
29.
by rubber_duck 6y ago
Uber is a different story, competition is a lot easier and it already exists all over the place (Uber isn't even that profitable which proves this, meanwhile app store is printing cash)
30.
by rubber_duck 6y ago
The store should set it's policy, law just ensures equal rights and review process for developers

More ›