405 karma · joined November 21, 2010
Have you tried Tree Style Tabs? Presents your tabs as a collapsible, hierarchical sidebar tree. Even when Chrome was kicking Firefox's ass in every other aspect, I stuck with FF because of TST. It's so much better than any other UI for tab management I've ever seen.
If you go through the steps of disabling the top tab bar and sidebar padding elements in user chrome CSS, it's more space effective than anything else too.
I appreciate Deno because I can ask job interview candidates what their thoughts are about it, and when candidates for senior positions don't point out any of the billion obvious reasons it's a stupid project for stupid people, it saves me a ton of time. Otherwise, it's a waste of time and effort, and all you have to do to convince yourself of that is look at the contribution history of the most prominent contributors on github.
I have never, not once, in my life as a developer wanted a project to die so badly.
Oh, you're making HTTP calls directly in React components? Well, you done goofed and that's not React's fault.
Basically, it seems everything they believe is "follow extreme programming as rigidly as possible and it will alleviate the downsides to being as short sighted as possible."
I've written an HTTP server from scratch before. I've experimented with scaling it up in multiple ways. I've admitted defeat and gone back to using pre-existing software. Other than scratching an itch to learn, I can't tell you one fungible benefit I got from that exercise as it relates to developing a REST API. Why should a software engineer who builds a REST API need to understand the inner workings of HTTP to use an HTTP framework? Why should a software engineer need to build a massive UI to understand how hard state tracking is to use React? Chances are someone is paying for that code which, by definition, is worse than it should be because it's an exercise in learning why the framework is necessary.
I'm not sure how invested your team is in Swift, but since we do nothing but Typescript, the investment in time (2-3 days for one the lead engineer) tweaking the linter has more than paid off ten-fold in the months since.
It's also a pretty impressive demonstration of the typesafe flexibility of Kotlin's DSL support, but that's another conversation.
RN isn't production-ready/stable yet either. They're about to do a major overhaul of the internals because of fundamental flaws that have been surfaced by the community. While it's possible to use RN in production, "stable" is a laugh... there are monthly releases and almost all of them have some kind of breaking changes, so pacing RN releases is a huge fucking hassle. For example, in the release that comes out this month (currently in RC), they changed the Native Module API so if you have any native code that exposes a JS API (and who doesn't?) you have to refactor a bunch of code. And because it's JS, the only way you get compiler errors is if you're using Flow.
Any tobacco store that sells rolling tobacco will have a variety of options available in sizes/densities/etc.
And it's a vape instead of smoking anything, but at these quantities it almost doesn't matter.
This isn't exactly true. PHP objects can have dynamically assigned members without having magic methods defined. e.g.
$foo = new stdClass();
$foo->bar = "baz";
echo $foo->bar; //"baz"
And now, with "closures", those members can be methods.