skysight-inc/HackerNews huggingface dataset:
Take the following as coming from a dilettante... I'm still trying to understand the remainder of the paper but felt like writing on the basics of the encoder/decoder/quantizer setup they mention.

I found this particularly interesting "To compress an image x ∈ X , we follow the formulation of [20, 8] where one learns an encoder E, a decoder G, and a finite quantizer q."

I feel like this is related to some of the standard human memorization/learning techniques. Example: I'm learning the guitar fretboard note placement in e standard. It's difficult for me to visualize the first 4 frets on a 6 string guitar with notes on each fret.

To help me memorize the note placement I develop various mnemonic devices (both lossy and lossless). I know I've memorized the fretboard sufficiently when I can visualize it.

Attempting to translate my reading of the paper I believe the following analogy is apt. My "encoder" operates on a short term image when I close my eyes after looking at a fret diagram. It produces semantic objects, i.e. an ordered sequence of "letters" or pairs of letters (letters that are horizontally, vertically or diagonally aligned). The quantizer takes these objects and looks at the order/distribution. The quantizer places more importance on some of the semantic objects than others (the fourth fret has 4 natural notes before an accidental). My decoder is interpreting the stored/compressed note information to try to produce the image. It may be off substantially, so I correct and repeat the process.

The process of optimizing what the semantic objects are, the weight each gets, and how I use them to derive the original image seems like a fairly good representation of what I do (though at least some of that appears to be fixed in the learning algorithm typically). Of course, analogies are just that and mine doesn't take into account the discriminator or the remaining "heart" of the paper.

I think the heart of the paper is that they're trying to determine through GANs a good way to both store the image and recover it while reducing bits per pixel and increasing the quality of reproduction. Using some classical terms, the GAN algorithm thus tweaks the compressor, the data storage format and the decompressor to optimize what should be "hard-coded" in the compressing/decompressing process or program vs what will be stored as a result of the compression program.

Very handwavey but I think the general idea is right?
What a world. Where we can't even take enough responsibility to be present enough to hear the "You are about to die" bell chime.

Imagine the possible breaking components in that chain too. Bluetooth can fail, satellite can fail, cell can fail,
WiFi can fail, a USB cable can fail, there isn't a single piece of connectivity technology that would make me confident enough to delegate alerts to another device.

There is also an inherent failure of alarms in general in that even very loud ones can be ignored if they give false positives even once or twice. There is a body of study trying to address it. Some of the most fatal industrial accidents occured because alarms were either ignored or even fully switched off. We aren't good with alarms.

I think the meat of it though is that unless Auto-pilot works perfectly then you can't leave it alone. And if you can't leave it alone then what's the point?

The sell for autonomous cars isn't that people are just so darn tired of turning the steering wheel that they would really rather not. It's that we could potentially be more productive if we could shift our full attention to work/study/relaxation while commuting.
Paleo Diet & Strength Training Biochemistry | Doug McGuff M.D.

https://www.youtube.com/watch?v=F7GB3h82tcQ
Car steered itself into a concrete wall. That is, by definition, failure. It doesn't matter whether it was properly following its coding to follow lane lines.
I am certainly not suggesting that you push porn on your child.

Rather, you seem to be suggesting you have to prevent your child from watching porn. I am suggesting forbidding porn, in private, is very likely to be counterproductive, because it is unlikely to succeed, it makes a reasonable human desire into something illicit, and is likely to instead result in a loss of trust + cause porn to be seen as forbidden (and thus attractive) fruit.

Separately, I am suggesting that when a child is interested in porn, that’s an opportunity for a conversation about the problematic aspects of porn, respect, and fantasy vs. reality. Loss of trust makes that conversation less likely to be accessible, or at least less likely for that conversation to involve your child actually listening to you.
> This is contentious. The city may be better off as a whole if it did not have 4,000 homeless people, many of whom were priced out of their apartments, due to tourism, foreign buyers, etc.

Homeless people existed in SF long before Airbnb existed.

> To many people, more tourism brings little to no benefit, while a reduced housing stock brings much direct harm.

Yes, to long term renters. There is no doubt that long term renters would prefer no short term renters existed. They would also prefer for all units to be rent controlled, or that landlords and property owners gave their properties for free.
> If I remember right, Linus's main argument against Tanenbaum was that the overall state gets so dispersed between the various services that make up a full-fledged OS, that eventually a microkernel-based system just gets unpredictable or starts performing poorly.

Well, large parts of the Linux world ended up with systemd, and I haven't yet met a person who had NOT had his fair share of issues with it.
It is not cost-effective to build much wind power in Norway, because of excessive cheap hydro power. Statoil and Statkraft build them in UK, where the price and subsidies are more favourable.
For me the realization that politicians just accept and use facebook for their own means instead of being opposed to it was a really bitter realization.

I was hoping that when they started realizing the potential, they'd feel threatened and require it to cease working that way. Instead they all run PR campaigns on social media, and they probably collect data on their voters too if they can.
It's just too disgusting to bear. Not just the US either, this is happening all across Europe.
Australian EMO releases initial report on Tesla grid battery system performance
It takes years. Whether people like it or not. It's never too late to start doing something about it.
Originally Finland, currently working in a multinational based in Germany. Same experiences in both countries, I've never felt any "soft" pressure of the kind described in this thread that'd call for such legislation.

On call hours are controlled by legislation though, at least in Finland. Compensation for being on call isn't just "included in your regular salary"; employers are required to pay 50% (IIRC) on top of that just for the fact that you're able to work (read: sober and not innawoods) during a certain defined time period, and if you're actually called in, salary for the actual overtime hours worked. Obviously this gets pretty expensive for employers though so they tend to make optimal use of their on call people, but at least the rules are pretty clear.
That grumpy project seems to have stalled in the last 6 months.

I feel like Google hasn't made much progress converting away from Python 2.

Python 2.7 is still required to build Chrome, for example, and I don't think there are any plans to change that.
https://bugs.chromium.org/p/chromium/issues/detail?id=61357

And, I believe they use 2.7 whenever they use TensorFlow.
I think of it this way:
Most car manufacturers are releasing their products on the public year after year, knowing full well that a decent percentage of people that drive away from the dealership will be killed by the thing they just bought.

Tesla is merely trying to take the next step in reducing that percentage.

Their strategy is sound and we so far have not come up with any alternatives that stand a remote chance of improving safety as much as self-driving. Even if they are largely unsuccessful, they are indeed trying to ensure the safety of the public.
Yes, the figure I gave was profit after all expenses. Since they’re condos, the association covers the heating/cooling system and everything exterior. I guess we’ve been lucky on the repair front, because the only thing we’ve had to pay for (in ~6 years) was a cheap dishwasher and toilet fix and occasionally repainting between tenants.
Ugh, hate that mindset.

My boss at my last job had the mind set of "refactoring only makes it different, not better". I asked him if I could spend some time refactoring our build system. He said no. I eventually did it anyway a few months later, spotted a bug due to the changes, and all of a sudden, build times were cut in half or in 10 in many instances.

Same story for a pretty nasty hunk of code we had for handling sparse arrays. Asked if I could refactor, got told no, did it anyway a while later, and all of a sudden a problem that had been considered borderline infeasible takes like 1 day of work.
Wow. You sure are an expert in alertness.
I've never driven a Tesla or any other kind of "autopilot" car.

But for the current kind of systems, what I would really like is something to take evasive action, not drive for me. I know some non autopilot cars have those systems in place, but not sure what more a Tesla car would give me in protection.

I guess I need to take one for a spin one of these days.
There is still an option to purchase a license.

However, I have to disagree about the "feature finished". We had a lot of customer feedback over the years and 1Password Teams is based on it.
This was, more or less, the driving philosophy behind BeOS. Therein lie some lessons for the prospective OS developer to consider.

Say what you will about how terrible POSIX is, Be recognized the tremendous value in supporting POSIX: being able to support the mounds and mounds of software written for POSIX. It chose to keep enough POSIX compatibility to make it possible to port many common UNIX shells and utilities over, while Be developers could focus on more interesting things.

So where were the problems?

One huge problem was drivers, particularly once BeOS broke into the Intel PC space. Its driver interface and model was pretty darn slick, but it was different, and vendors wouldn't support it (take the problems of a Linux developer getting a spec or reference implementation from a vendor and multiply). This cost Be, and its developer and user community, quite a bit of blood, sweat, and tears.

Another big problem was networking. Initially, socket FDs were not the same thing as filesystem FDs, which had a huge impact on the difficulty of porting networked software over to BeOS. Eventually, BeOS fixed this problem, as the lack of compatibility was causing major headaches.

The lesson: if you are looking to make an OS that will grow quickly, where you will not be forced to reinvent the wheel over and over and over again, compatibility is no small consideration.
It's a decent talent grab: Gabe Sibley of Zippy is a world-class state-estimation guy, formerly at Zoox, a SV self-driving startup, a professor at U Colorado at Boulder, postdoc with Newman's robot/driving group at Oxford, CS PhD @ USC.

A 4-year old video of academic-mode Sibley on autonomous navigation https://vimeo.com/88273779

(I'm not Sibley and have no conflict of interest: just work in related areas).
I had something similar, twice. Once I was in the elevator when the emergency phone started ringing. I picked up, and it was the Seattle Times trying to sell subscriptions.

The other time, same elevator, it was someone asking for a specific person that I had never heard of.
Supporting evidence: the Rampage movie, "Toys of the 80s" (or whatever that Netflix series" is, etc. I'm not ashamed that my 6 year old knows who Orko is and that five kids can drive a sword weilding group of mechanical lions to defend the universe.
whb07 is not valuing all government actions at zero dollars.

They are valuing all government actions at substantially less than the original value in private hands.
They probably shut down the self-driving thing because they literally stole all of their code from Google.
It has both. Mach system calls are negative, BSD system calls are positive. The BSD side has system calls for stuff like fork() that would otherwise be pretty clearly in Mach's domain.
Hyperbolic VR using Raymarching
I always found the mercurial ui super easy.

The error messages are clearer, it is multiplatform, all the advanced functionalities are there, a nice graphic interface exists.

I really do not understand why git won, apart from github.
The great thing about a keto diet is you can eat vastly fewer calories, without being hungry. A couple of eggs and a few slices of bacon will set me up for the entire day, such that I forget to even think about eating until after I get home from work. A bowl of cereal or a plate of pancakes with the same number of raw calories will have me murderously hungry by 10 AM.
Parsing with `nom` seems like a pretty aggressive introduction to Rust :)
Rust specifically because it has the zero-overhead safety properties via the borrow checker. This is something that no other safe language has, as far as I know. They generally either make you deal with a GC if you want safety, or deal with raw pointers and manual memory management if you want low overhead.

And the borrow checker, along with move semantics by default and the Send and Sync traits, help with several other aspects of safety as well; the Send and Sync traits encode information on what can safely be moved or shared between threads, and move semantics by default (and checked by the compiler, instead of at runtime as in C++), make it easier to encode state transitions on objects in ways that you can't try to perform operations on an invalid state.

But as others point out, Zircon, the Fuchsia kernel, was written before Rust 1.0 was released, and even after Rust 1.0 was released and stable it was still a bit rough to work with for a little while.

If you were starting a new project from scratch today, I'd seriously ask why not Rust, though of course there are other reasons why you might not choose it. But given the history, and how new Rust was at the time when this project was started, it makes a lot of sense.
We disagree on the definition of dweller, cities require more than just vacation seekers to function. And the longer term renters aren't taking up those dwelling since it's more profitable for owners to rent out short term, but the reason that anyone wants to rent short term is because it's an interesting place to be, which it won't be if it's all people on vacation.

I'll call this the Ibiza Quandary.
> The manufacturer gets to specify the conditions under which they consider their product to be safe and suitable for a particular purpose.

No, they don't, otherwise they could disclaim everything.
Those companies are a nicely disguised cover to maintain one's status quo. An online marketer once pointed out a Jenny Craig(?) advertisement: "Eat all the food you want!" Busted.
There's an argument to be made that a process that allows more time for evidence to be gathered to stop the bad projects would generate a more net positive result. That argument does, of course, relegate the machinations of bureaucracy and the pressure from various stakeholders to a bit of a spherical cow, though.
I'd say adaptive cruise control is actually better in the sweet-spot. I have a Subaru with adaptive cruise control and find it rather beneficial in freeing up my attention from trying to carefully micromanage the throttle / brake to actually focus on more important things. It has lane-keeping assist, too, but that is more of a backup safety feature than an autonomous feature (and indeed I wouldn't want lane-centering functionality except in really slow traffic jams).
Also, the car behind the bus disappears. It looks like it's been photoshopped out. This is unexpected behavior from a compression algorithm. Users are conditioned to expect the quality to degrade uniformly across the whole image.
AFAIR, you can only update jobs (collections of single containers) and allocs (pods inside of which jobs will schedule and run: you need to state that job J lives inside alloc A, otherwise it will run in an anonymous, implied alloc). There aren't other objects you can manipulate, actually.

Configmaps don't really exist, although something similar is achieved with a job that has a second package holding just the data. This is why I think multi-image containers should be implemented, but also a reason why they haven't been yet: configmaps cover some use cases. When a job replica (task) gets updated or rolled back, both packages change in sync. On Kubernetes, you'd use version numbers in the configmap name (but you need to worry about garbage collecting unused ones).

Services live outside of Borg entirely. GSLB has its own push mechanisms and only consumes Borg's lists of containers that comprise a given Borg job.

From the paper:

> A user can change the properties of some or all of the
tasks in a running job by pushing a new job configuration
to Borg, and then instructing Borg to update the tasks to
the new specification. This acts as a lightweight, non-atomic
transaction that can easily be undone until it is closed (com-
mitted). Updates are generally done in a rolling fashion, and
a limit can be imposed on the number of task disruptions
(reschedules or preemptions) an update causes; any changes
that would cause more disruptions are skipped.
Some task updates (e.g., pushing a new binary) will al-
ways require the task to be restarted; some (e.g., increasing
resource requirements or changing constraints) might make
the task no longer fit on the machine, and cause it to be
stopped and rescheduled; and some (e.g., changing priority)
can always be done without restarting or moving the task.
What's really interesting is that there are a number of video game franchises with nuanced backstories that have spawned successful and surprisingly well-written novels. So it's definitely possible to take a video game and turn it into a book. And there are plenty of books that get turned into excellent movies or TV shows (of course, there are plenty that get turned into bad ones, FWIW).

Books like Eric Nylund's Halo: The Fall of Reach, Greg Bear's Forerunner Saga (Halo again), or Brandon Sanderson's Infinity Blade: Awakening are all pretty well-respected and did well in terms of sales. Probably because they manage to avoid falling into the temptation to simply recreate the game experience as a book. They use the game's plot as a starting point to influence the story without dictating it.

Of course, by deviating away from "the game" as fans experienced it, you risk alienating them because the final product doesn't match up with what they expect. And because the same fans are probably the reason why the studio is willing to finance the movie in the first place, I can sort of understand why Hollywood repeatedly tries to hew closely to the source game even though that approach has repeatedly screwed them.

The peculiar thing is that they face a somewhat similar situation when they turn a book into a movie. And yet, Hollywood is more than willing to take risks and deviate away from the source material when necessary. So what about video games in particular scares the studios away from doing the same?
I suppose its perhaps how they marketed the feature. We have parking assist feature in many cars, there's a reason its not auto-park instead. If it really was a feature to help attentive drivers avoid accidents, it probably would have been called a driving-assist tech and not auto-pilot.
Not really, but like I said in response to other comment, we’ve had very few repairs. There’s never been more than ~1 week gap between tenants — near university housing is always hot, and the management company only gets paid if the place is occupied. They usually have the next tenant signed before current one leaves. In one, we’ve had the same tenant for the whole time.
Thanks for the reply & good luck, I'm rooting for you guys! :D
Uncharted and last if us are really poorly written imo. They are full of the clichés, they just cover it up with good voice acting. Uncharted makes Indian Jones look like citizen kane by comparison.
"Humanity makes contact with the galactic community of intelligent life and claws its way to respect and acceptance with the help of plucky heroes". That is a very common trope employed by many, Star Trek among them. It's a fine set of games but as a story for a movie, it's as generic as it gets.
Ledger Investing (YC W17) Is Hiring a Statistician in DC
The big takeaway I got from this is, be wary of any organisation that attempts to isolate workers from each other and prevent communication. The old divide and conquer. People talk about people who cut off their significant other, maybe people need to be more aware of this tactic on a wider scale in other organisational contexts.
That doesn't really seem super relevant, given that the parent comment seems to have been using template metaprogramming in the same way -- to just mean any template code.
So you’re saying that Tesla drivers are only educated by marketing materials and ignore what the car says every time they engage the autopilot feature?
Despite What Zuckerberg’s Testimony May Imply, AI Cannot Save Us
Both professional marathon runners and professional sprinters are huge outliers who start with particular atypical body attributes and then aggressively train to optimize for very narrow competition.

Then on top of that you are talking about men's macho/sexualized fantasies about their body shapes, not their carefully considered decisions about practical abilities to train. Most people don't actually want to look like pro sprinters in practice, but would prefer a more typical fit body shape.

There are many physical activities which will result in different development. How about dancing, rock climbing, hiking, martial arts, rowing, yoga, ...? And how about just moderate exercise/practice instead of pro-level devotion.
I'm not aware of any exclusion for emergency/public service transmissions. Lots of police departments have been switching to encrypted P25 to prevent scanners and the like.

Basically anything other than the cell bands is trivial to receive and decode w/ $15 SDR dongle.
There is some help in weight control from lean muscle mass. Fat needs about 2 kcals/day/pound to stay alive. Muscle needs something in the 20 kcals/day/pound range to stay alive. Also, having a good amount of lean muscle mass naturally leads to a more active lifestyle in general. But these are still minor compared to basic diet.
Im speaking from personal experience. From not being able to write to the SD card with updates to the Gmail Outlook/Exchange Sync being broken in Oreo, to gmail messages being delivered hours or days late due to doze and GCM messaging. It's not parroting when its true.
> It's a feature that is in development

there's something fundamentally wrong in releasing that to the public then, your authority for vehicle safety should be VERY concerned about this, people getting killed aren't "bugs to iron out".
At this stage almost any sum would get you the assets and keep the operational part of the company going, and you could pretty much name your terms: valuation, op plan, everything. If you were already an investor you might know about something useful in the IP, perhaps something that mgmt doesn't care about.

Note I said assets. Technically the company doesn't appear to be insolvent in which case instead of an ABC you could basically strip what you want away from the obligations.

And those laid-off people? They got 60-day notice; certainly some of them have already jumped but probably not most of them and in such a restructuring you might be able to retain the ones you want (which could be all of them).