hvis

Check that you have `libjansson-dev` installed, or whatever is the equivalent on your system.

Also: indentation, beginning-of-defun/end-of-defun navigation, and probably Imenu later.

All the basics of major modes that up until now have been implemented using bespoke algorithms, rewritten ad-hoc for each language.

> As mentioned above, the service we were building was a fairly straightforward CRUD app. The expected load on this service was going to be on the order no more than a few queries per second, max, through the lifetime of this particular system.

Naturally, there is a reason people opt for higher level languages like Ruby/Python or at least Go or Java/Kotlin to write apps like this.

People using laptops, for instance.

When the completion is not context-sensitive, it's not really what "code completion" is taken to mean these days (the last decade, at least).

To quote the article:

  Did they work? Yes! Performance on lightly loaded systems was about the same as OSSpinLock but on loaded ones, they provided massively better responsiveness. They also did something extremely useful for laptop users: they cut down power consumption as a lot less cycles were wasted having the CPUs spinning on locks that couldn’t be acquired.

To no one's surprise, one has to use Apple's undocumented APIs to be able to match Safari's power use.

It's better than the "copyright theft" slogan pushed by the media.

The moderators only really need to review the videos already flagged by the automatic process, and the classification ML thingy can add the timestamps with positions the "objectionable content" is featured at, so the mods wouldn't need to view the video in whole.

How many of the videos are flagged down, though, we probably don't have any solid statistic on that.

I would have liked this kind of promise, but for the general public this marketing message might have sounded differently: "We might shut down before 2024".

Even if some people are kind of used to this happening, stating it more obviously might have a negative effect just as well.

Your compensation bands (linked from https://handbook.sourcegraph.com/benefits-pay-perks/pay-expe...) are not publicly available.

> It'd take one or two graybeards with too much free time to sustain Atom.

Perhaps. Does Atom have said graybeards? The motivated ones are hard to come by.

I've worked with Visual Studio, and Eclipse, and NetBeans for a few years.

Then tried Emacs while learning Clojure, and after a few to and fro, stuck with it.

This was before Visual Studio Code (or Atom) became a thing, though.

All "properties" are functions too (methods, to be exact). There is no difference.

`attr_accessor` is a macro which defines two methods.

I suppose they wouldn't be able to boast 14 hour long life with a better screen.

Definitely agree, though.

I suppose you and I cared about different aspects of it.

But at least some of the things you enumerated should be possible to add. Maybe file an issue, see what happens.

Unity was a great project, but not all is lost.

I've been using this GNOME extension for years, and it's been very solid: https://extensions.gnome.org/extension/1287/unite/

It emulates Unity quite well (removing the titlebars on maximized windows, among other things).

The vast majority of users of Telegram come from (and reside in) a country whose jurisdiction you probably wouldn't trust. Most of its developers, too (though they have relocated).

I love how half of the top10 replies here (including #1) is about Firefox not being supported.

See Google, cross-browser compatibility is important.

There aren't many companies with that capability and scale outside of US.

And the States are watching you anyway: most of the Internet resides there. Even the websites that don't are likely using Cloudflare or etc to save on traffic.

> I have no reason to trust random American companies more than my local ISP. I don't trust the USA more than I trust my own country.

You know you are quite fortunate to be able to say so.

Firefox is a project with global impact. A lot of people around the world can benefit from DoH.

It's a good political move.

And Mozilla doesn't live on donations anyway (they are used to finance "initiatives" of various sorts).

Immunosuppressed humans are a minority. And each of them would be less likely to get infected (at all) if the regular people around them took vaccination seriously.

Regarding Omicron, there is some cause for hope: so far it does seem to produce less severe illnesses.

Without any solid guarantees (e.g. laws), you're just out $300 and back where you started.

Not having every block be a separate value makes it easier for the Ruby VM to optimize such code without escape analysis (which is something that's pretty hard to do in this language).

Don't have to allocate the container => don't need to use the heap one more time. Nor access the block's code through that indirection.

Same thing with methods: they aren't objects, but you can create an object pointing to a method any time you need one.

> And Firefox has multiple backup of sessions to the point even if your previous session was corrupted you can still recover a session saved slightly earlier.

Yup. You might have to root around in the profile's directory, though, which not every user knows how to do.

But it being a possibility is absolutely great.

> This was partly done because there are people ( like me ) who have hundreds if not thousands of Tabs opened and they ( me ) complain a lot about it.

Same.

Browsers these days routinely persist the contents of the current session to disk, exactly to defend against a crash (computer or the application itself).

Of course, bugs and disk corruption happen, but you need more than a computer crash to lose all your tabs.

> I assume there's some reason why the parser can't read `{ x, y }`, as ruby is notoriously hard to add syntax to.

Something in the parser using the colon after the first identifier to disambiguate between hashes and blocks, probably.

> Crypto mining hardware is >100% efficient

It also makes the hardware depreciate (simply with the passage of time, but also because of the particular usage), which in practice effects the balance and can easily turn the monetary efficiency into negative.

I guess that's what made Twitter rise in popularity as a source of news: difficult to stuff much filler in 140 characters.

> It's just that enough people saw enough value and purpose in it, to go out and get it themselves.

This happened at the time when no other browser vendor drove any kind of serious marketing campaign. Even so, Firefox only reached 30% market share at its peak.

Then Chrome shot out, backed by Google's marketing budget, bundled with popular software installers and featured at the "Internet home page": "Still running Firefox? Upgrade to Chrome now!" (quote is approximate, but very close)