I'm guessing what happened here is neither maintenance nor (planned) demolition.
133 karma · joined January 19, 2017
I'm guessing what happened here is neither maintenance nor (planned) demolition.
Is there any more information about such instances or is that insider knowledge?
(Client must specify compression support)
A good AQ test would hopefully control for this? Though my understanding is that IQ doesn't control very well for practice either. It's a hard problem.
1. Act as a preprocessing step for any existing C++ file
2. Output perfectly servicable C++ in the case where you want to move away.
Additions like the "known" keyword make this look badly thought out.
In any case, the weakness of C++ in most cases is compilation speed, not typing speed. Even in the ideal case I can't see this adding more value than it detracts (preprocessing speed + buildsystem complication + extra dependency).
In any case, I don't know of any modern political system in which this important issue can be addressed directly -- rather than letting each authority silently make decisions based on their own values.
It's also worth noting that the absolute value of people's lives (in terms of what's spent) changes depending on who's doing the spending. This is the same as saying "money is worth progressively less as you get more of it". That's unlikely to make the topic more approachable.
From the perspective of society, even assuming that someone declared brain-dead could be revived -- maybe with some future technology if they just keep the body functioning -- at what cost does it make sense to end the life?
Are there other cases where the unpleasant (edit: was "distasteful) subject of the cost of a life (as valued by society rather than Bill Gates) comes into play?
Also, that was a music CD with malware, not a software application. I'm sure the DRM for many games was comparable, but they still had to mind their manners somewhat.
I miss when my money mattered.
Mozilla dropped support for Tab Center a while before Quantum IIRC. Another addon took its place, but then was dropped by its developer with Quantum. Supposedly [1] will allow transition from the older addons. I'm looking forward to finding out once 59 is out.
[1]https://addons.mozilla.org/en-US/firefox/addon/tab-groups/ [2]https://bugzilla.mozilla.org/show_bug.cgi?id=1423725
Didn't read much, but hopefully it allows hiding without unloading.
Patiently waiting..
My point about bookmarks and pocket not filling my use-case (even if I dropped read/do later) stands -- I really do want multiple switchable tab contexts.
As a reluctant user of tree style tabs (holding out for the restoration of tab groups), I disagree.
I usually have different sets of tabs open:
- A set for each of the 2-3 projects I have active this month
- Casual browsing
- Read later
- Do later
This adds up easily to one or two hundred tabs -- and these aren't bookmarks. Bookmarks aren't gone when you close the tab, which is the desired behavior for all the above cases.Pocket or similar (ignoring my refusal to use a 3rdParty service for my own data) would only be useful for do-later and read-later.
With tab groups I had a perfect setup which supported /all/ my use cases in one go. With TST I can roughly approximate this with a top-level tab for each (it's not great).
Bookmarks need to be replaced with something that covers a wider range of use-cases without having to cobble together a bunch of different workflows.
People know about bookmarks and pocket. Most people who are actively searching out extensions are not avoiding learning a different workflow (obvious if you think about it). I've gone through many different workflows, and I'll keep testing out more. Tab groups was the best thing yet for me.