skysight-inc/HackerNews huggingface dataset:
if it is stacked screens, I don't see any reason it will work horizontally only. I believe the view angle is still very limited. I'd love to use this for Skype chat or something.
Is there any plan to make this a partner product ?

It's limited to 10 Concurrent Build for obvious reason, making it impossible for startup who want to create CI services on top of this product due to limitation.
You can't be charged with crimes they can't prove. It's why comedians and public figures can openly admit to smoking weed.

I think you have to much faith in the justice system. They don't have to "prove" anything. Once they arrest you, they can easily intimidate you into taking a plea and the overworked public defender won't be of much help.
Are you asking why the author chose not to include one?
I am not convinced that you really need lambda and all that complexity. I also don't really like the characteristics of Lambda, taking forever to wake up and limited debugging. A $5 DO/Hetzner Instance can already do a lot if you pay a bit attention to performance. I run a small Golang Api on DO for $5, using DynamoDB and some Cloudflare Caching (free) and it can handle quite a lot of traffic.
If only Claire (or one of her "unaffiliated" super-PACs) could somehow blame this on something Josh did during his 1.5 years as AG...
You're not alone.

This is like those DB abstraction layers because "we need to change DB", but in the end almost no one doesn't the products lifetime.

Also given that most of our clients don't use these fashionable cloud APIs, rather their own infrastructure, makes also not that much relevant to me.
If you haven't seen it, I highly recommend the movie Ingrid Goes West. It's this article in the form of a brilliant dark-comedy.
this made me think of the book disciplined minds. while not directly related and is more focused on behavioral, managerial, and systematic issues, it is a very interesting look into who controls the direction of research, work, and perspectives.
Compression is needed and probably not difficult given that not much extra information is rendered comparing to normal display given the limited view angle. Probably only twice as much as bandwidth needed if compression is done properly.
Yes, there are lots of famous examples. E.g. John Chowning invented FM synthesis for musical applications but had to assign the patent to Stanford where he worked as a researcher: "The FM patent produced about $22.9 million in royalties for Stanford University (largely via the sale of FM chips for soundcards)." With a patent date of 1975 and a duration of 20 years, they must have received royalties until 1995 off every OPL family chip (used in Ad Lib, Sound Blaster, etc) and all the Yamaha instruments based on FM synthesis (I believe Yamaha had an exclusive license in that market). That's just one particular example I happened to remember, but every tech-focused university probably has a large portfolio of these sorts of patents.
Just add the "2FA" tag and the banner goes away :)

I was saying doing that is easier than adding 2FA through 1Password.
> Let's allow the investigation to continue

This is a strawman - no one is calling for ending the investigation prematurely.

> before rushing to judgement.

How soon is too soon to "rush" to judgement that these boats are unsafe?

The NTSB report regarding the 1999 Arkansas sinking [0] noted problems with their lack of reserve buoyancy. Certainly weather played a factor in the Missouri sinking, but so did the design flaw that causes it to sink or capsize much more easily than a modern boat of equivalent size. That design flaw has been known publicly for almost 20 years.

The passengers who drowned in the Missouri sinking weren't wearing life jackets. [1] The 1999 NTSB report recommended removing the canopies of these boats, but if the canopies couldn't be removed, then they recommended not using life jackets.

And the main subject of the article is the crash from 3 years ago in Seattle. That happened on land, caused by a broken axle. [2] It turns out the person who designed the "stretch" duck boats didn't have any formal engineering training, and it's not a huge step to imagine that stretching a vehicle in that way could lead to increased stress on the axle.

This isn't rushing to judgement. This is understanding the context of decades of previous incidents for better insight into the most recent one.

0: https://www.ntsb.gov/news/press-releases/Pages/NTSB_Determin...

1: https://www.cnn.com/2018/07/22/us/missouri-duck-boat-tragedy...

2: https://www.seattletimes.com/seattle-news/ntsb-ruling-expect...
Awesome geography knowledge here! This was fundamentally a weather and engineering issue though. There’s just no way to get to safety when you realize the storm is too much for you in a slow and clumsy craft like this. You have to make the decision not to go out at all if the forecast is potentially dangerous. I’ve never seen weather swells on these small lakes large enough to swamp anything (big speedboat wakes are another story) so I would imagine the wind caught the awning and tipped it enough to take on water. Then the awning drowned everyone when they couldn’t overpower the bouyancy of their jackets to get out from under it. Bad decision by the driver to make the trip caused the accident, and the life-jacket policy combined with the awning design made it fatal.
> We're too lazy to read a page of regulations / not track users by default
> It's well known that Ivy League engineering is pretty shitty

Citation needed.
This appears to be a way to formally verify the correctness of concurrent programs when translated from a modified version of C (RC11–"Repaired C11") to native machine code. At least that's what I got from the paper–I didn't read it all the way though, I just skimmed it.
OP's usage and explanation of the term are spot on, and you miss the whole point if you conflate technical debt with bad design. One of the causes of technical debt is a change in requirements, and changing the initial requirements doesn't mean that the design was bad.
(Eng Manager for Go Cloud) The APIs and HTTP server released today all work on AWS as well as GCP and support for Azure is a top priority but didn't make it for today.

Please see the comment from our PM regarding Azure: https://news.ycombinator.com/item?id=17604358
Siemens secures large service contract for the two major Dubai airports
Microsoft went from multiple smaller repos for windows to one large one: https://blogs.msdn.microsoft.com/bharry/2017/05/24/the-large...
"You won't believe these 10 hate groups that Marc Zuckerberg refuses to ban, donates to!" > "Facebook stands firm, bans extremist nationalist hate group: <No longer available> from platform!
Right, i missed the oauth2 scoping aspect.
Freezing Python’s Dependency Hell
working as dev with academic teams, I usually use many repos for "damage control" as git-ignorant scientists will dump irrelevant files into a repo.

with that in mind, is monorepo is a universally good approach or is more dependent on good behavior of team members than polyrepo?
Google branches google for releases. Otherwise, you would end up with version skew across dependencies, which would be a mess.
It all makes good sense in a scenario when the user is sending some data. But for static websites, when they are only visiting a website?
Fedora to Ubuntu
We are switching today from Fedora to Ubuntu Workstation. Anyone else recently swapped? What do I need to know?

For us, the lack of nvidia-docker and anbox constituted the proverbial straw that broke the camel's back.
He's suggesting developers extract the keys from the official Twitter client and use those, bypassing the usual developer agreement.
There's lots of IP shenanigans, and it's not axiomatically true that the PI owns their IP. My university, which is a pretty middle of the road state school, has several people who work on this full time, and they're genuinely busy.

The tricky part here is that if you call it a "gift" you don't get charged overhead, whereas you do if you call it contract research, which is what it actually is.
Err... pretty much every monohull sailboat ever manufactured will "sink immediately" if the hull is punctured. Keels are heavy.
While Hossenfelder is well within her wheelhouse criticising the search as wrongheaded, members of the public reading and forming an opinion on the proper course of physical research is less than useless.

It's exactly the same thinking that leads people to conclude that global warming isn't a problem, because they found a climate scientist who also disagrees.

Unless we all, en masse, want to go get physics degrees to properly critique the arguments, the only responsible thing for a member of the public to do is trust majority opinion. It can be wrong, certainly, but it's vastly less likely to be than any of the dozens or hundreds of minority opinions which oppose it.
Ask HN: Simples way to create a personal Website with Blog
I am looking for a good looking, mobile responsive website and blog that I can get up in 10min. I don't want to worry about hosting or fooling around with Wordpress... Any suggestions would be appreciated.
While I understand your point, looking at that code, the first word into my mind isn't "trivial".
Ask HN: Where can one learn about the history of the internet and the protocols?
I would like to read about the initial proposals, email exchanges, discussions, about why any specific technology or protocol was built, who all were involved - designer, funders, contributors, etc.
History, timeline, discussions, proposals - accepted & rejected, ideas - accepted & rejected, philosophy, restrictions.
In general I would like to read about all the technologies, but want to start with the internet and the TCP stack (protocols).
Professors do this all the time. The pressure to keep the lights on and your grad students funded is not to be underestimated.
"a-dub believes P" != "P is well known"
One of the big advantages of the monorepo is actually that it prevents technical debt from accumulating. If a change somewhere else breaks your code, you can't put off dealing with it -- you are forced to fix the issue immediately.
You do have to be pessimistic or cynical to think that the words good and evil have no real meaning, or even if they do then it’s not worth trying to use them because nothing is perfect and clear.

Refusing to deal with nuance and disagreement in a complex world might even be a good practical definition of pessimism. It’s a catch all “what’s the point of even trying?” excuse.
I hesitate to blame it on lack of credentials. Much of engineering history has been made on piles if dead bodies resulting from mistakes made by fully credentialed engineers, even with advanced degrees.

Engineering school does not confer at least two things: common sense and experience. These qualities are independent from academic learning.

If the designer/modifier is found to be at fault it is far more likely to be due to a lack of research and common sense than a lack of schooling.

I mean, building a boat like that that can sink if swamped and traps passengers inside is just plain stupid, degree or not.
I don't think that there is the one size fits all solution especially if you can't expect basic knowledge about git
The security consultants that work for Verizon aren't the same folks that allowed the Yahoo/Oath credentials dump from half a decade ago.

Verizon has a reputable security consulting arm that competes with Bishop Fox, FireEye, Rapid7, NCC Group, and other recognized computer security firms. Verizon is a massive company and isn't just wireless and home internet.
I don't think the original purpose was to be able to behave like a boat, more for fording deeper rivers in combat situations.
> They (any service with a large user base across many devices) are at a serious disadvantage of not being 100% in control of app upgrades across the legion of devices and app versions supported. They are just as likely to break a legitimate user's app as yours (even higher, imo).

Yes they are? Alternative apps use the official API, their internal services use their internal API's, which are also likely versioned. So if the internal DM API has an upgrade, the website can change to the new version while the mobile app is using the previous version.

youtube-dl and Youtube++ are already solved problems. The fact that you have to sideload it means the user market is tiny and at this point I highly doubt YT even cares anymore.

> I also see these gray area tools as an important check on the power of the platforms to not abuse their dominance.

This is the weirdest thing you've said in a whole lot of weird things. YT proved how powerful it was via demonetization of so many creators videos. Nobody could do anything about it, primarily because the real power behind YT is that creators don't have an alternative, not users.
I met someone who was on a clinical trial for Ambien. He'd pass out almost immediately, but first he'd see crazy wild hallucinations. But only for like 15 seconds to a minute.

When it was finally released on the market, the dosage was a fraction of what he had take in his clinical trial.
They don't often willingly get their memorizes blanked though.
Fair point. I however don't agree fully. One could argue that there's not as much urgency in adjusting quotas for EU and similar allies but they too need to be checked because of the way they treat US co.s especially those in the tech sector.
No, the tweet points out how this is specifically because Google uses a deprecated, older version of a standard that only Chrome supports. It’s absolutely not a question of Firefox or Edge being “just slower,” it is a question of using a feature that is literally only implemented in Chrome and that other browsers have agreed not to implement.
> Well, take a simpler case: A program that takes a lock and then reads a file specified by the user on the command line.

I'm having trouble seeing the use case under that Unix Philosophy constraint. I admit I might not be imaginative enough, but a program/utility that would be normally expected to operate on its own locked file (by being asked to do so by the user) still seems incongruous.

> it was less code to write, while thus causing every user of the abstraction to have to write tons more code if they want to have correct code.

Actually, that's a completely valid design decision and philosophically compatible, even if you happen to find it distasteful.

It's one of the (caricatured) tenets of "Worse is Better" which has been credited with the (original) success of Unix over more "correct" competitors http://dreamsongs.com/RiseOfWorseIsBetter.html :

> Simplicity -- the design must be simple, both in implementation and interface. It is more important for the implementation to be simple than the interface. Simplicity is the most important consideration in a design.
> Correctness -- the design must be correct in all observable aspects. It is slightly better to be simple than correct.
> Consistency -- the design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either implementational complexity or inconsistency.
> Completeness -- the design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. In fact, completeness must be sacrificed whenever implementation simplicity is jeopardized. Consistency can be sacrificed to achieve completeness if simplicity is retained; especially worthless is consistency of interface.

It seems like advisory locking has made a "worse" sacrifice in each category, in favor of the purported benefit. There's even a reference (though I don't recall if it's in that essay, specifically) to making the user do extra coding work for correctness.

Of course, there are plenty of critics of "Worse is Better" or the "New Jersey approach", including the author of that essay. However, his whole point is that it improves survivability, which, arguably, was still important to Unix in the 80s and maybe even into the 90s.

> not thinking it through. Locks are for coordinating concurrency, the unit of concurrency is the process, so locks are held by processes. Oh, and we have to clean up locks that aren't released by the process! Well, let's do that when the file is closed

It's absolutely not thinking every possible future scenario and corner case through, but that, I would argue, is the opposite of "braindead". It worked, especially for the use case you described, which seems perfectly reasonable for early Unix (and adherents to the Unix Philosophy of any era).
What common usage was redefined?

Where would you substitute "bad design" or "ineffective design" into the comment?

Perhaps this will help: http://wiki.c2.com/?TechnicalDebt
How much an app development actually cost?
Thanks! Yep, there are quite a few newsletters I am adding. Also, working on a feature for users to request a newsletter they'd like to see on newsletterhunt
I'm a big fan of "Vocal Vibes" by Richiere, "Mellomania Vocal Trance Anthems" by Pedro del Mar, and "Uplifting Only" by Original Uplift. Found all of them through the Digitally Imported / DI.FM streaming service.
BLU Studio G4 Is the Latest $99 BLU Phone with Android 8.1 Oreo Go Edition
Replacing 90s C Linux Utilities with Python
I would love to see something similar applied to Mexico. The scale would have to be a lot bigger, and I guess it would be a lot more dangerous since we are literally facing wars for territory over here, taking soldiers out of the battlefield wouldn't look appealing for the drug cartels.
Vuejs Framework Update Slider Component
Jonathan Morrison (https://www.youtube.com/watch?v=Y-p9-QZSdPM)
I call this "Google Imposter Syndrome". Because Google (insert Facebook, Apple, Amazon, etc) has success with Monorepos (insert gRPC, Go, Kubernetes, React/Native, etc), it must be a great idea, we should do it. You see this everywhere. Also known as an Appeal to Authority.

My personal opinion: very few companies will hit a point where sheer volume of code or code changes makes a monorepo unwieldy. Code volume is a Google-problem. But every company will have problems with Github/Gitlab/whatever tooling with multiple repos; coordinating merges/deploys across multiple projects, managing issues, context switches between them, etc. And every company will also have problems with CI/CD in a monorepo.

Point being... there are problems with both, and there are benefits to both. I don't think one is right or wrong. I personally feel that solving the problems inherent to monorepos, at average scale, is easier than solving the problems inherent to distributed repos. The monorepo problems are generally internal technical, whereas the distributed repo problems are generally people-related and tooling outside of your control.
Sorry, but as someone who has been in orgs that do both, mono repo is a mistake. Constant needs to pull unrelated changes before pushing, pipelines requiring to grab the whole repo for dependencies, etc. I understand the arguments for mono repo, but never think it's nothing that outweighs the cons.
You said:

“Do you have any reason to believe that higher taxes and spending will lead to better outcomes, or higher net societal welfare?”

...And the historical example of Western European social democracies like France, Germany, and the Scandinavian states prove this.

>Which 75-year-old policies are you referring to, exactly?

Nationalized healthcare, massive investments in public transportation and education, higher welfare floors and labor protections.
Up and Running with AWS EC2, S3, Linux and Deep Learning
I’ve read worse low and middlebrow dismissal of the book.

Always considered the Lorax as a resident of the area, not a nosy distant neighbor, though didn’t think about it deeply until now.
Heh, sounds like I made some decent choices then ;) I just saw your comment now, but in the interim picked up Calculus Made Easy and a short 'manual' on differential equations that John Baez recommended somewhere. I also recently acquired Div, Grad, Curl, but from the looks of it, I won't get much out of until after my little Maxwell's equations project. Thanks!
At its very widest the channel is less than a mile across, so there is less than half a mile to go. Holy crap these things are slow, but apparently that would take less than ten minutes, less if aided by gale-force winds. Did ten minutes pass between "I can't handle this storm" and "oh shit I've killed us all"? Probably!

https://www.google.com/maps/place/Table+Rock+Lake/
> Technical debt isn't about whether you like or understand a particular approach, it's about whether the codebase as a whole is still maintainable, whether the bugs make sense and are fixable, whether new features can be added without stabilising the whole code base.

It's not about that either ... it's about things that were put off, generally for valid reasons at the time.

> It's never the new feature that's the problem.

What do you mean by "problem"? Many new features are inherently problematic.

> If the new feature can't be added in a good way, it's the old codebase that has unhandled technical debt.

That would only apply to waterfall development with infinite foresight. In the real world, wise people employ the YAGNI principle.
If your cheap Chinese USB charger shorts out and starts a fire in the dash of your Cessna, that is a major issue, and given the rate that Chinese USB chargers do short out, a reasonably significant risk.

The last thing we need is flaming Cessna's dropping out of the sky into heavily populated areas.
Yeah, that whole GDPR thing really came out of nowhere, eh? :)
It's not just devops that you need to pull off a large monorepo; the other big thing is a strong testing culture. You have to be able to rely on unit tests from across the code base being a sufficient indicator of whether your commit is good. AND a presubmit process that can compute which parts of the monorepo get affected by your diff, and run tests against them automatically before committing your diff.

Google not only has the above but also has a strong pre-submission code review process which catches large classes of bugs in advance.
Ketamine absolutely stops you from feeling pain. It's one of the things that's dangerous about using it recreationally, you can injure yourself and not even be aware of it. Your leg could be bleeding out, but you're too ketty to notice and just keep partying on.

I haven't seen anybody seriously injured form this, but I've heard second hand stories.
Time for antitrust to break Google up. At the very least force the divestiture of both Chrome and YouTube. And obviously given the case in Europe, Android as well.
>If they've seen someone live up to a stereotype
The thing is that stereotypes are stereotypes for a reason. That reason being that they apply well on majority of cases.

For others who think that showing educational videos is going to change minds, think why you call some videos propaganda and others educational. Now try and think what the person you are trying to influence will think about your video. You'll see the problem quickly.
But even in Mexico really violent places (50+/100k/yr) are pretty highly concentrated in known areas. Not all Mexico is violent, like not all Maryland is violent, like not all Honduras is violent (it happens in pockets) often fueled by the drugs trade.

It would be interesting (and a welcome outcome) to see if this insight and method of fighting crime is accepted and used by locales high relative violence rates.
Not remembering committing a crime has never been a valid defence thus far and we have drugs that cause far more extreme behavioural changes besides just memory loss.