skysight-inc/HackerNews huggingface dataset:
I didn't say C# was exclusively used by boring companies. I made no claim that it was a bad language, quite the opposite (I would probably have it in my top 5 back end languages). I'm not using boring as a derogatory adjective-- just as catch-all for non-VC/FAANG companies. If you look at "boring" or mature companies such as insurance or consumer good companies, where technology is viewed as just a tool to solve the business objective, rather than the feathers of the goose laying the golden eggs, you will find different priorities-- such as programming languages that take into consideration backwards compatibility, scalability from the start, development time and general support ecosystem.
Yes, just `git fetch` first, then you can take a look at what the merge would look like before actually applying it. `git pull` is approximately a synonym for `git fetch && git rebase origin/master` (if origin/master is your upstream branch)

If you don't like the results of merging, you might like rebasing better, as it linearizes the new history, so really you end up only re-applying your changes (the ones you presumably know better) on top of the new version of their changed code.

Rebasing gets a bad rap. Rebasing is what SVN and traditional SCMs would call a merge, and merge is really the weird crazy complex operation.

If you decide to bail halfway through `git rebase --abort`

Or for a particularly hairy merge you could use a temporary branch you can always abandon

Funnily enough, older SCMs already dealt with this by having commands like `lock` to advisorily lock a file.

The best workflow to adopt to make merge conflicts less painful is that if you have an area of the codebase with a lot of merge conflict, break it up into more files so you are less likely to be making simultaneous changes. Frequent super hairy merge conflicts are an architecture code smell. You should only have serious merge conflicts when you really are working on the same logical units, and in that case you should communicate.

In a sense I'm advocating you put into practice Whoever's Law, that says that software tends to take on an architecture that reflects the org chart. If I and 10 others are constantly editing the same thing maybe we need to figure out if we can divide up the code's responsibilities so that we aren't always editing the same parts, or simplify the truly atomic inseperable parts so that the merge conflicts end up looking trivial (eg, a configuration type line that lists a bunch of strategy objects to link in, with the actual code in those strategy objects spread in across different files)

Or, alternately, after thinking it through maybe you find it's just irreducible and you have a "9 women can't make a baby in 1 month" scenario. In that case maybe you should communicate more so that everyone isn't working on it at once. If all 10 of those people have useful essential input, do some upfrong design / pseudocode and come together in a brief meeting or asychronous design doc review to get consensus on what to do before putting in many hours into the low level details, and then have just 1 or 2 people work on actually implementing it.

At the end of the day, serious frequent merge conflicts are just a code representation of org chart level issues, so they are solved with communication.
I think I did. That person was dealt bad cards (assuming they are sufficiently motivated and getting the most out of their set of circumstances), and their mission in life now is to overcome whatever challenges are currently preventing them from having a higher paying job (of which there are plenty).
Thanks for your suggestions. We've just had another look at the upcoming priorities for Hydrogen and I can confirm that both of those things are planned for the not-too-far future! Hard to commit to exact time frames, but you've been heard :)
Which people? The ones that sold the car while claiming it had not been in an accident? The people who want to sue now? I would guess the sales people and lawyers are in different areas of the company.

Could this be a cultural thing at the company or, at least, the part in China?

Remember, Tesla builds cars that you aren't allowed to have non-Tesla folks fix them and Tesla has turned off features in used cars because they didn't think it was bought at a high enough price (even when it was sold used with the features). This has happened in the US.
As far as I know, there aren't any languages which provide a way to do this out of the box. If a language wants to provide an environment where no stack overflows can happen, then it needs to provide a runtime where the stack programs use is transplanted over to the heap as it gets too large (or maybe it just starts out there). At this point the answer is that you only need a stack big enough to hold your runtime (which you can engineer to be sufficiently small always).

Of course you can imagine a language where your function signature includes how much stack space it takes up. The stack size being recursively calculated by looking at all the functions your function calls etc.

If recursion is included, then you're correct that this would require solving the halting problem. The obvious solution would be to just not allow recursion. Although, if you also consider languages like Idris (which are technically sometimes not turing complete) you can setup a termination checker and then certain rules can give you an upper bound on how long a recursive function will run (and therefore how much stack it takes up).
Wow, I'm really sorry to hear that. We absolutely don't support that use case, and especially with this version, it's pretty hard to measure with that kind of exactness in a way that could be used for that kind of abuse. Honestly - this kind of thing really motivated us to make these changes with this new version. It's pretty clear to us that productivity has less to do with time in seats and more to do with balance.
Do you know about the shortest fully conforming C compiler?

#include <stdio.h>
int main(int argc, char*argv[]) {
printf("ERROR: resources exhausted!");
return -1;
}
I have "research scientist" as a job title. It's a thing: https://deepmind.com/careers/jobs/469515
> There are rules about what and when you can do, say, eat, wear, everything.

How long have you been in the workforce and what sort of places have your worked? I have personal experience with employers that had rules on one or more of these.

Also, I lived in a monastery, as a monk, for a while. Don't discount the article. Your whole day is not prescribed, you can socialize outside the community, and there are discussions around rules. You even get some evenings off to go out and about.
This does need detailed management analysis from an ethics POV. IF the facts, as stated, are true, I can not think of any US Tesla manager taking this stance.
In fact, if that fact was concealed and the customer lied to, the customer was right.
Now is it possible, in the USA or China for a vehicle to be sold as pure and unsullied? Yes it is - if some one lied to the customer/Tesla that it was unsullied. I think this is illegal in the USA - is it also illegal in China - or business as usual in China? There is a Reddit thread called r/Chinesium which details a legion of low quality items entering into commerce that are unworthy of sale, that should have been rejected at production time or have inherent low quality workmanship.
Thus Tesla needs to rebuild bridges in China, cease this Streisandish litigation and move on, making sure that there is never again a recurrence of any more cases like this.
All this said, have there ever been any cases like this in the US production flow?
I like Tesla, I like Elon, I like the way he acts and thinks, and I suspect he will deal with this with some sort of managerial imperative, might I say ramrod? I am not sure how much managerial control is exercised over Tesla China by Tesla US?
Managers and the entire management culture in China seems to place a high degree of credence to 'face', or appearance. This leads to managers hiding errors instead of facing them and solving them - a bad practice.
You can sideload the apk and activate it using another phone with a valid sim card. Even if it is a feature phone.
Right. With 64-bit ISAs you can address 2^64 bytes, but... you can't exactly have 2^64 bytes. At some point the system will fail. How it fails is important. A ran-out-of-resources errors is a lot better than undefined behavior resulting from random memory corruption.

And yes, portable C has finite size_t. Therefore portable C must fail in some way when limits are exceeded.
This is false.

(I am a former Mozilla employee who was there when the layoffs happened)

This is what I know about what happened there:

There were two enterprise IT teams with similar duties but different purviews. When management was deciding on layoffs, they decided to unify those two teams. Unfortunately that meant that there were redundancies.

My heart goes out to those who lost their jobs, and they have every right to be upset.

But the inferences being made as a result of the resulting tweets just weren't true: this notion that all security teams were wiped out is false. And there are now others assigned to threat management.

Furthermore, the security teams that work on Gecko and Firefox were left mostly if not entirely intact.

The entire hardening/sandboxing team was still intact: https://twitter.com/gcpascutto/status/1293519587967983616

TL;DR: Don’t base your understanding of an organization’s capabilities off of one tweet.
Hey, PM for R2 here.

We're still deciding on how we want to handle caching. We integrate with Workers, so manually caching is always possible. The catch is we're currently building for strong consistency - if we added a cache in front, we'd weaken that - so it will likely be a configuration option we add later.
Packery · Draggable Layout
This looks like something I might use on my own but if it was forced on me at work I'd find another job...
I can easily imagine compiler+linker being able to forbid recursion and statically calculate maximum stack needed. Probably you need to ban general function invocation via pointers... methods on objects could be fine, you just evaluate all virtual method override combinations.
Toyota's Woven Planet Acquires Renovo
I don't use it, but it seems to be free, with an optional "pro" subscription for some extra features. The subscription pricing is only mentioned on the App Store page, and appears to be $3/month or $30/year.
We could enable the linter in production to silently log problematic queries without actually affecting their execution.

If we used separate db users as you're suggesting, any query that we didn't catch beforehand (e.g. via our CI builds) would cause noticeable problems for our users, which is something that we want to avoid.

Additionally, switching to a separate user account would require holding open twice the amount of connections to each database server (old db user plus new db user), which probably would be fine but is still a lot of additional connections at our scale.
So the CIA is it’s own thing. That said that’s fd up.
Estimates are not commitments. I know young devs are preyed upon, but people can't be pushovers in the workplace. It's really detrimental to all, so we need to support reason above rituals and rigid processes.
Would this be the feature that's causing my ASUS Motherboard to automatically install ASUS Armoury (some silly OEM app) every time I update my BIOS?

It's frustrating to see more and more control of our machines being taken away and hidden under layers of firmware/hardware/closed source code - especially if it's exploitable like this... It seems like a very short-sighted bug!

However, I could see this feature being somewhat helpful for OEMS (Dell/HP deploying their "support assist" softwares for their devices if it's uninstalled/new copy of Windows.
This is particularly amusing considering Google's extreme lack of v3 documentation. Their samples and examples Github, for example, has only 2 examples, iirc. They also introduce a lot of silliness like the inability to nest content scripts within folders.

Not to mention all the limitations of the Chrome browser. The continuous difference between console.log and console.dir. The former only shows you a very limited view of JS objects while the latter is what Firefox uses as the default for console.log - a full view of the object you want inspected. Then there's the inability to edit and resend network requests. The only workaround is to copy the request as a fetch request, dump it into the console or snippets, re-edit it there, and then send it through the console. Of course you'd have to parse the response in the console too instead of being able to see it in devtools.

And then there's Chrome's complete lack of proper proxy support. You could start the browser with command line flags in order to enable a SOCKS5 proxy, for example, but that requires you to close your existing browser session and open a new one.

Finally, how is it that we have nearly exact dates (2022-01-17 and sometime in January 2023) for V2 sunsetting but the dates for implementation of actual features needed to migrate away from V2 have no solid expectation date? Isn't that putting the cart before the horse? From the article:

"In the coming months, we'll also be launching support for dynamically configurable content scripts and an in-memory storage option, among other new capabilities."

"In the coming months"? The v2 sunset date is just a few months away! Why not ensure that the current feature set is fully functional and adequate to replace v2 before blocking v2 extension submissions?
It's not true. See my reply to their comment.
PS: I read TFA after writing this comment (ha) and it sounds like this tool is a great way to detect areas of code that could most use the kinds of refactors I just discussed. Just following the pain would work too though, albeit with a slightly larger lag.
Haiku activity report – September 2021
> Also found a couple that reject sign-ups when their name is in the username part.

This is how you know not to use that company.
Ok, so OP asks where are all the Show HN's and all the comments are advertising people's past Show HN's instead of addressing why OP isn't finding many of them?

Maybe I am overthinking this because I resent advertising disguised as something else.
>the late Dan Kaminsky

Ehhh... I forgot he was the "the late Dan Kaminsky"

:-(
The IPv4 internet is merely 2^32, and people have been scanning that whole thing for years now. The /112 is referring to IPv6 addresses.

Plus the copy about not hammering other networks won't matter when you're trying to scan entire /64s that are behind one home router or something. That's gonna get noticed. You can't really scan IPv6 like you can scan IPv4, the math I gave is part of why. The code to do it is trivial, but the hardware just isn't there.
Money is an issue though. If you want to study how every disease affects neuro-divergent middle-child women of native american descent then the cost of doing research will sky rocket. Nothing would ever get done.
Poo, for anyone who is interested
And yet they haven't. If it becomes a problem, I could switch domains with a little work.
panta rei - everything flows
Totally understand. The online component makes it challenging for a lot of folks. Fortunately this new version requires less in the way of constant online support, and we're definitely considering developing an offline-only version of this new app in the future.
try pale moon https://www.palemoon.org/ , basilisk https://www.basilisk-browser.org/ or dot https://github.com/dothq/browser
Aside from Shodan's neat trick of infiltrating the NTP pool, are there any papers/blogs on successfully exploiting known properties of IPv6 (network prefixes, MAC vendors etc)? However I think about it it seems too massive
Many animals eat poop for various reasons. For some because it's important to their digestive process (rabbits). For some, because of less important reasons (dogs).
Yep, they should throw out the window all these years of MySQL experience and expertise and start from scratch :s
It's the lack of unions and cheap wages. Southern states are famously lax on workers rights and business regulations.
Anyone know what is normal in other countries? I grew up grinding and sanding our old lead-painted house. I think its probably common.
What a biased take on this: s/vandalize/read
Without ICs, these devices have to rely on mechanical controllers, which are much larger, more expensive, less reliable, less efficient, louder, and really worse in ever metric.

I think your sentiment is not to produce wifi-powered, ad-driven refrigerators, and yeah, I can agree with that point. But the core ICs in these devices have been there for decades and do provide substantial, tangible benefits.

I can't speak for every device, but I've replaced the circuit board on a few appliances over the years and they are mostly generic boards with really cheap, ancient chips produced by brands most people have never heard of and sell in bulk for a quarter each. These are definitely not cutting the cutting edge designs that Intel will be building here. So let's not throw the baby out with the bathwater.
I can never remember the title of books sorry, other than The Mom Test because it was on HN recently[1]. Probably Company of One mentioned it too, I read that recently.

They all say in some form or other: find where the people with the problems hang out, learn how they express their issues with the problems, fix the problems, explain to them in their own style and wording how your thing solves their problems, customers

At least that's how I remember it, pinches of salt all round on the exact learnings please!

[1] https://news.ycombinator.com/item?id=28667439
I had the same thought, most of the argument here seems to be about screen space. I think at some point we're all attracted to the idea of having a bunch of monitors so you can feel like some kind of multi-tasking movie hacker, but the reality is that if you learn to use your window manager efficiently, one monitor is almost always all you need.
You can write programs that depend on no libraries at all, not even an SDK. They just need a compiler binary (and a machine to run that--x86-linux, x86-darwin, jvm, or even a Wasm engine) to compile, and compile to a binary that also only needs a machine to run--no shared objects, external jars, etc.

The language has no builtin classes, interfaces, or functions. In contrast to say, Java, where the language (and compiler) know about java.lang.Object, java.lang.String, etc. The compiler knows how to compile classes, but it doesn't know the name of any built-in ones.

Virgil is really designed to build the lowest level of software. Thus all my focus on low-level things like calling the kernel and mapping stacks, etc. The only thing that depends on more than just the kernel is the test suite, which uses bash and a little bit of C.
How did you read ebooks with BeeLine back then? There's one ebook app [1] (confusingly called ReadMe!, which is the name of a YC company) that has integrated our tech. But the ebook space has been a trouble spot for us because the platforms are so closed/DRM'd.

In other news, we just released an iOS Safari extension, now that iOS 15 allows extensions. If you liked using BeeLine, I'd highly recommend checking it out, especially since we made it free for early adopters! [2]

1: https://readmei.com/

2: https://apps.apple.com/us/app/beeline-extension/id1571623734
New media car sites like Jalopnik and The Drive (which has a lot of former Jalopnik writers) are closer to Medium blogs than the NY Times. Sure, there's an editor, but in general the authors just post their own hot takes, and articles on Jalopnik will vary dramatically in slant (and quality) depending on who wrote them.

For example, Bradley Brownell loves EVs, including Tesla: https://jalopnik.com/the-2021-tesla-model-y-is-the-universal...

David Tracy highlights interesting Tesla engineering: https://jalopnik.com/the-tesla-model-3s-superbottle-easter-e...
https://jalopnik.com/the-tesla-model-ys-octovalve-and-coolin...

And Jason Torchinsky definitely isn't entertained by Tesla and Elon Musk:
https://jalopnik.com/teslas-pr-department-hasnt-responded-to...
https://jalopnik.com/teslas-ai-day-event-did-a-great-job-con...
Tail Call Optimization & allocating their own stacks, generally.
Direct or reflected light is just light. Same stuff.

What matters is the content and quality of the light spectrum.

LED lights or even LCD screens can be designed with a more or less healthy spectrum depending on the priorities of the manufacturer. But this is an economical problem that can be regulated.
Is gray water reuse happening at scale?
In practice I've found that people claiming site X works in chrome but not in Firefox is usually incorrect, and unless you actually try it you won't know. I use Firefox and have done for 15+ years, and I genuinely can't remember the last time I had to switch browser to use a page or webapp.
Elon is one of the most litigious CEOs. Fish rots from the head.
Anyone else not want to cut themselves off from physical reality for hours at a time for productivity purposes? I like looking away from my screen and seeing my dog and cat on the couch. I like looking out my window. I like being distracted by a car driving by. This sounds awful.
Just went through sign-up flow. Heard of the product for years + interested in it.

One note - I have a bit of an idiosyncratic schedule. I work 9-6:30 and then stop for the evening (dinner with family, put kid to bed) and resume work ~9pm typically. I'd love the ability to block off that time slot (6:30-9) but keep space for working before and after.

Beyond with, excited to try it out.
This feels a bit like those “FOR TOBACCO USE ONLY” signs at headshops who sell bongs.
Before you owned a nice full-featured i9 proc. You could go on Ebay and sell it for all its power.

Tomorrow, you buy your new shiny basic i10 proc. You then pay extra to unlock the fast multiply for our games, the fast simd for you AI and the upgrade for 4K decoding. After a while, you decide to sell on Ebay. Well your nice shiny software defined features are now worthless. Well not for Intel which has the opportunity to sell the same stuff twice or more.

What would be incoherent is for Intel to not juice this technology even more. Why not have a limited pool of licenses and let people compete for them monthly ?.

The problem is that the boundary of ownership is getting shifted, and by the look of if the consumer will loose.
I’m working through the book now and a lot of chapters say something like “Download this public MySQL dataset from the internet and convert it into Postgres using pgloader”. The whole time I was wondering why the author didn’t just find public Postgres datasets but it makes a lot of sense now
Time to abandon stack as a 'display'? That's why they overflow (mostly) - lots of large items or lots of recursion and local variables.

Also having the addressable method arguments in the same space as the return address, allows a whole host of other bugs and cracks.

I have long thought, the return stack should be a memory region un-addressable by the code except via call and return.

Local method arguments could then revert to ordinary allocations or some other check-able allocation, and have normal error recovery.
That makes a lot more sense. you can always just install initially and then use opkg to install local packages you scp across in the future as well: `opkg install path/to/package.ipk`

another option would be to just grab the files from the package itself and extract them to the device, and then manually run the install script steps as required. They are basically just gz tarballs.
Could you say more? Is your issue with the license's content or branding?

I work at Airbyte and am genuinely curious about your view.