krisdol

It depends on what program you're talking about. The previous iteration, Binge ON, capped streaming videos at 480p, but you could opt out on your account settings page.

The current iteration, One, caps Netflix, YouTube, HBO and other services at 480p, and you have to pay $25/mo for an "HD Add On" to get rid of the cap.

Sprint caps different types of apps (even games) at different bandwidths as well, and there is no option to get more than 480p from them.

There is nothing good about this.

T-Mobile has that set up in the US. Luckily you can at least opt out, which I have. T-Mobile offers various unmetered streams if you use the apps, but they degrade the quality of the stream. I believe all youtube streams become 480p, for example. I don't trust that they don't or won't affect other sites in some negative way.

Frankly, I'm happy with the data plan I have and I have no need to bargain off portions of the internet so that my ISP can closely monitor and manipulate certain sources.

It is every non-employee-owned company.

My company makes a profit because it pays me less than the value my labor creates.

The default settings for my org were private membership and I hadn't realized it until later on. There may be more developers who just are private

It's a quote from the book Nineteen Eighty Four

Bietstandgegenwitgeschaft is real though

Did you try calling one?

Because she's a female CEO and any news-provider's comment sections are absolute cesspools.

In a time-series datastore, you may have to replace a set of invalid/corrupt events within an index. Having IDs that are in some way deterministic from the source data, you are able to replace the invalid documents by ID by simply re-indexing that time period with your patch applied. This is the most simple and least risky solution, with minimal downtime

If the IDs are UUID, then the easiest way to fix the values is to drop the index and re-create it, making all of the other data in the index unavailable as it's being recreated.

The less-easy way with UUIDs is to select just the broken events, create new patched events, delete the old events, and insert the new ones in the right index. But you'd have to branch off of your regular indexing logic to do this, probably writing a separate script. Of course if you make a mistake, you may end up with either duplicate documents or loss of data, compounding the original problem.

So I agree, have IDs that are deterministic (that they can be recreated using some known formula and source data, for example: documenttype_externalid_timestamp).

I think they're only saying it because TIFU is a colloquial acronym for "Today I Fucked Up" (this is how I read it too), not intending to insult your abilities.

>I only really know the finance and software fields well and there its very acceptable for an employee to leave for a competitor

Maybe in California. Non-competes are a reality pretty much everywhere else.

You can use .map to call await on every element in the array, or define a new function so you don't have to write that all the time:

    const awaitAll = (futures) => futures.map(f => await f);

edit: this is wrong but I can't delete it. Haven't used async as much as promises.

Without a non-pre-rendered demo video actually demonstrating how it works (and to a lesser extent, without color), it seems like a pretty steep price point for paper.

Android + Web + Desktop is not multiple platforms?

By that logic, you could say that leiningen and gradle hide the very awful maven build system, and maybe if they didn't exist, the daily pain of working with maven would be enough that it would actually be improved.

But it's been well over a decade. Maven is maven, npm is npm, make is make. Yarn is doing a good job now of being the new and improved build system for JS projects, and create-react-app seems to be using it under the hood.

Eventually I may care about what compilation flags lein passes to maven in order for it to compile my clojure project into jvm bytecode, but that day hasn't happened yet and I've been glad not to have to set those up with every clojure project I start. The same now applies to react apps.

I can agree to that.

HN isn't generally liberal leaning. HN is generally libertarian leaning. Not all of us, of course, but the sentiment here is very pro-business.

I have too many. But it works well for me. I've worked on too many languages with the same editor, so I've got... Front and back-end JS tools (linting, tern autocompletion, builds); clojure with a repl and parinfer, paredit; some rust and elm plugins that can probably go since I just experimented with those mainly. Linter for terraform. I also use atom for general note taking, so I've got a couple plugins for that.

About 10 seconds of startup opening a directory, from terminal to loaded workspace. I'm on a MacBook Pro (Retina, 13-inch, Early 2015). I have 76 community plugins installed.

What web technology does this use, specifically, that prevents firefox usage? Or is it just a chrome plugin they decided not to port?

A lot of that is available in "text editors" like Atom (and I assume VSCode). Of course, it depends on if someone wrote a plugin for your language of choice.

That sounds abysmal. Slack is the only thing on that list I keep open., and I've gotten a pretty good set of notification settings configured.

That line is getting really blurry with both Atom and VSCode. Haven't used VSCode, but the only feature I recall missing in Atom right now is refactoring; and to be fair, last time I used a real IDE (XCode), I couldn't refactor there either.

Why are you assuming that we're OK with it? The top 3 or 4 threads here are critical of it.

What would they do if you just don't carry your phone with you when you fly? One could ship their phone or put it in checked luggage.

They are not just looking for data at the border, they are imaging the phone and keeping those records for god knows how long and with what level of security. That is a level of privacy I'm not willing to give up, let alone the risk of having company confidential data end up in unintended hands.

I'd just like to interject for a moment. What you’re referring to as Fuchsia, is in fact, GNU/Fuchsia, or as I’ve recently taken to calling it, GNU plus Fuchsia. Fuchsia is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.

Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called “Fuchsia”, and many of its users are not aware that it is basically the GNU system, developed by the GNU Project. There really is a Fuchsia, and these people are using it, but it is just a part of the system they use.

Atom + ProtoREPL[1] + Parinfer[2] is surprisingly good for clojure, without having to learn a swath of form manipulation keybindings. I haven't tried combining those with vim bindings. This (https://gist.github.com/jasongilman/d1f70507bed021b48625) is more or less how I have it set up.

1: https://github.com/jasongilman/proto-repl

2: https://github.com/oakmac/atom-parinfer

Wow, I didn't even know DisplayPort daisy-chaining was a thing

- FLAVOR: Ubuntu Desktop

- HEADLINE: Provide a rolling-release flavor

- DESCRIPTION: What keeps me from fetching too many packages from the Ubuntu repositories is that major package updates take 1-2 OS releases to get into the repos. This makes OS upgrades more difficult to execute because so much is changing at once, but also made me constantly seek workarounds, install from source, add third-party ppas, etc. when I couldn't have a newer version of some package.

- ROLE/AFFILIATION: Software Engineer