I routinely have several thousands of tabs opened on my devices, and I never considered myself a hoarder.
At some point you adopt a workflow where every browser activity starts with opening a new tab. Plus, so many websites have broken browser history management that it’s easier to open all links in new tabs, too.
I do close tabs on occasion, usually when I see that the device starts to struggle. Closing all tabs helps make things fast again.
Browsers tend to take open tabs into account when I search for stuff, and it’s nice to be able to enter a few keywords and get redirected to an existing tab. Saves me time for page reloads.
Sometimes entering the same keywords into a search engine does not land you on that article, though, so closing tabs as rarely as possible pays out for me a few times a year. But it’s ultimately not that important and I don’t keep tabs around for the sake of it.
> I routinely have several thousands of tabs opened on my devices, and I never considered myself a hoarder.
You seem serious, but it sounds a bit funny!
I also often open links in new tabs. It's also a bit faster than e.g. going back in history. But I do close tabs after I'm done browsing that site or otherwise don't need it. I'd start to feel lost with a lot of tabs open (say, hundreds), not knowing what is actually relevant, what kind of research is "in progress", how to keep track of them well etc.. I do use multiple browser windows and vertical tabs in Firefox.
> Browsers tend to take open tabs into account when I search for stuff, and it’s nice to be able to enter a few keywords and get redirected to an existing tab.
Similarly, I mostly receive suggestions from my browsing history and use that a lot. I've disabled any suggestions from search engines, since they are usually useless.
Meanwhile here I am at stage 0. I work on several projects where we are contractually obliged to not use any AI tools, even self-hosted ones. And AFAIK there's now a growing niche of mostly government projects with strict no-AI policy.
I’m luckily in a situation where I can afford to explore this stuff without the concerns that come from using it within an organization (and those concerns are 100% valid and haven’t been solved yet, especially not by this blog post)
As someone who never saw Mad Max, Slow Horses, Cat’s Cradle, Breaking Bad and only saw Waterworld when I was a kid all the references in this post went completely over my head, and I just think of words used in there as their own terminology. Like, if non-engineers read about chemical production.
The article was pretty Ok. Kubernetes has it's own share of obnoxious terminology that often comes up as "we name it different so that it doesn't sound like AWS". At some point you just accept the terminology in relation to the tool you use and move on.
It's actually remarkable how with the success of TypeScript so many other dynamic languages switched to gradual typing.
Erlang and Clojure were the early ones, TypeScript followed, and now Python, Ruby, and even Perl have ways to specify types and type check your programs.
> "a static type check is just a stand-in for a unit test."
This is not an original argument. Rich Hickey made a similar argument in his "Simple made easy" talk in 2011, though his focus was on a fact that every bug that easiest in a software system has passed unnoticed through both a type checker and a test suit. And even before that similar ideas of test suits being a suitable replacement for a type checker have percolated through Python and Ruby communities, too.
I distinctly remember that the "tests makes static type checks unnecessary" was in fact so prevalent in JavaScript community that TypeScript had really hard time getting adoption in its first 3-4 years, and only the introduction of VSCode in 2015 and subsequent growth of its marketshare over Atom and SublimeText got more people exposed to TypeScript and the benefits of a type checker. Overall it took almost 10 years for Typescript to become the "default" language for web projects.
Perhaps, their own hiring pipeline is suffering, too. With most companies out there cutting internships and hiring of people with no experience "because AI will replace them" for the past 2-3 years we probably having a large dip in number of prospective candidates with 2-3 years of experience today.
Historically, these candidates have been the hiring sweet spot: less risky than brand new engineers, still small enough experience to efficiently mold them into your bespoke tools and processes and turn them into long-term employees, and still very cheap.
DDG has been around for a long-long time, and when it started Perl was an old fashioned choice but still very reasonable. Even if they moved to other languages they probably still have old bits of Perl code running somewhere.
For about first 5-10 years of its existence DuckDuckGo also promoted their use of Perl, and afaik they contributed to Perl development.
It's notoriously hard/expensive to get a car/standard bike parking space. Even at home, and probably wherever you go if the place has any popularity. Think about parking car in Shibuya.
So a small vehicle has a real intrinsic value, not as simple as a parking a bicycle, but pretty close.
PS: Honda also makes the Monkey, which is ultra cute and pretty popular
I think I've seen that Honda one around NYC. Had no clue what it was. It just looked like someone was riding a brief case and that's basically indeed what it is.
* They came with a mail and chat (IRC) clients, a download manager, a set of browser dev tools, and in the age of limited internet traffic all of that was smaller than a single download of Firefox.
* Their dev tools were the first that allowed remote debugging. You could run Opera on your phone (Symbian, Windows Mobile, early Android) and debug your website from a computer.
* They were the first browser to sync your bookmarks, settings, history, extensions across devices.
* They were the first to add process isolation, albeit initially on Linux only. If an extension crashed your page it didn't take the whole browser down with it. This was later added first by Microsoft in IE8 and then by Google in Chrome.
Their browser was a brilliant piece of tech and a brilliant product. Too bad that the product couldn't survive under pressure.
At some point you adopt a workflow where every browser activity starts with opening a new tab. Plus, so many websites have broken browser history management that it’s easier to open all links in new tabs, too.
I do close tabs on occasion, usually when I see that the device starts to struggle. Closing all tabs helps make things fast again.
Browsers tend to take open tabs into account when I search for stuff, and it’s nice to be able to enter a few keywords and get redirected to an existing tab. Saves me time for page reloads.
Sometimes entering the same keywords into a search engine does not land you on that article, though, so closing tabs as rarely as possible pays out for me a few times a year. But it’s ultimately not that important and I don’t keep tabs around for the sake of it.
reply