425 karma · joined February 19, 2013
The opportunities for advertising are amazing, since you can place the consumer RIGHT at the locations they’re most likely to make an impulse purchase.
Who’d opt into something like that? lol. Most of America.
Most popular dynamic languages don’t use garbage collection under the hood anyway. In Python and many other runtimes, it’s primarily reference counted.
It hasn’t been a problem for me in over a decade in a multitude of languages. On Java codebases? I’ve witnessed some frightening levels of sloppiness that are only solvable with a profiler.
Often, I find the loudest containerization zealots tend to write the most fragile code. “Impossible” environment errors aren’t handled because: “Docker.”
When asking, WTF are you using package X? “You shouldn’t care. If doesn’t affect you, because Docker.”
Docker is great in skilled hands. Everywhere else, however, it can become another way to skip over best practices and tightly couple code to “perfect” environments.
There are so few articles about Docker anti-patterns, but the list is huge.
I sat in a meeting where the execs were all complaining about Apple’s unfair business practices re: their inability to do terrible things in background tasks, and their frequent app rejections / review process.
In this case, Apple saved countless phones from being bricked by one of the worst enterprise app developers. Some of the restrictions help to prevent first class assholes, like them, from publishing wholly defective garbage.
It seems like a personality type that’s generally careless and self important. Texting isn’t much more distracting than the thousands of other unsafe things people do.
It limits the scope & necessity of domain knowledge to be scattered about everywhere. The core logic is easy to reason about and there’s no tight coupling.
For example, if I’m calling libcurl directly in C++, I’ll create a generic adapter. Auto completion isn’t adequate for that library anyway, unless you can remember the docs.
If it’s some unwieldy “does everything” internally developed monolith by a team from hell, the same applies. Encapsulated composition.
Lower profit and higher expenses is the only way, but given the risks of any ambitious title, small studios are nearly always flirting with bankruptcy as it is.
There’s no easy answer, but time to market and risk will suffer.
It’s easy to put in long hours when everyone else does and you genuinely enjoy their company.
It’s easy to forgo pay, when you have equity.
You’re just never going to get the opportunity to work creatively with a talented team at Wells Fargo. It’s a totally different experience.
If you’re concerned about a work/life balance or compensation, it’s not for you. I’d hate if game development turned into a typical corporate 9-5, and was inclusive of all skill levels.
Pay is decent, if you’re established and are at the top of your game.
I strongly suggest all developers disable completion & tag jumping, not because I’m an elitist, but because it forces you to write better code. Not a troll. I’m serious.
On projects I’ve worked on that started with Intellisense, they quickly evolved into being unmaintainable without it. It’s an asset to skilled hands, but a debilitating crutch for the novice.
It’s like never operating a vehicle without a GPS. You never develop certain types of skills.
Everybody else I know, however, has had nothing but headaches.
They’re the same reasons I’ve seen people fail at using Cassandra, Redis, or Spanner. If you can’t adjust to the limitations and paradigm shift, you get no benefits. And an ORM often makes everything worse.
The “no” in NoSQL doesn’t seem to stop people from modeling join relationships in Redis, or chaining distributed queries with fully consistent writes on Cassandra.
I’m on a project right now, where a developer has selected an ORM for PostgreSQL that forgoes joins. They’ve managed to generate about 100 queries, in one case, where a single query is all that’s needed. 2ms vs. 800+ms. That individual is incapable of using something more complicated. Substituting Mongo as-is will make everything worse, and they’ll triumphantly proclaim how terrible NoSQL is and then write an article.
I feel confident using Mongo for any task. I don’t feel confident letting most of my peers use it.
There are a LOT of legitimate gripes, but no article I’ve read mentions them. It’s always the same superficial complaints from ten years ago. If you can’t get past those, choose another tool. End. Of. Story.
I’d love to write everything in Python & Rust, personally, but it’s just not a viable option for many types of projects.
With the smallest amount of self discipline, C++ is safe, expressive, maintainable, cross platform, and interoperable.
I rather like that it’s not forcing training wheels on my every statement and condescendly telling me what I’m allowed to do.
Of course, it means that code from the article’s example is possible. You can write code like a sloppy asshole in any language. Don’t blame the scissors if someone decides to start running while holding a pair.
One way they’ve grown is by allowing small companies to easily add their products to their stores. Good luck getting Macy’s to sell your custom line of trollface shirts. Shelf space is live or die for small brands. Amazon has a lower barrier to entry without the strong arm tactics big retailers have used for years.
Retail is often a middleman operation with exclusivity deals and price fixing. Brick and mortar is failing for so many reasons. It’s not that there are restrictions preventing fair competition, it’s that the old guard is slow and incompetent and likely won’t survive the old model of exclusivity on goods.
Edit: At least on a Sun workstation
When I write a C or C++ app, if I use libcurl and a library I’m using does as well, it links to the same shared libcurl library (mapped in RAM) as all other running processes do as well. With NPM, you can’t share libraries across process space and you’ll often even find the same packed being imported multiple times within the same app. In JS, it’s like statically linking all of your dependencies, but even less efficient. It can be argued that this is as good as it is bad.
When you build a code ecosystem atop JS, the underlying inefficiencies multiply as each layer is added. VS Code is more efficient, but even 192MB is still pathetically bloated.
Expect Atom to eventually approach and surpass 1GB of RAM, not less... at least in the short term.
Reading about the latest headlines is like sitting in a timeshare presentation, only it drains my phone battery and crashes my browser.
It’s a shame that the media is so bad at producing media. The quality is down, the delivery is terrible, and they want more money.