skysight-inc/HackerNews huggingface dataset:
I've been exploring this technique more over the past year and I really like it - https://datasette.io (code at https://github.com/simonw/datasette.io ) is a more recent and much more complicated example.

Extracting links from markdown and using them to populate some additional columns or tables at build time would be pretty straight forward.
It wouldn't even need AI for massive benefit. Simply automating and authenticating data about which factory is producing what using what inputs would have been absolutely massive.
For those who are not familiar, a bit of context.

Pico-8 [1] is a "fantasy console" - basically an emulator for gameboy-style portable game console but without the actual hardware.

The emulator itself is a paid product and it comes with tooling and documentation to create games ("cartridges"). You can find many of them on itch.io [2].

[1] https://www.lexaloffle.com/pico-8.php

[2] https://itch.io/games/tag-pico-8
Pretty close. They started offering Ubuntu preinstalls on 24 May 2007.

https://www.delltechnologies.com/en-us/blog/15994-2/
The SAT-I 800 pt math section was trivial. I didn't study for it and aced it. Big whoop. The written part is more difficult. The GRE is mostly easy too. I wouldn't brag about such things. Abstract math proofs covering nearly 20 pages and deriving time-dependent Schrödinger wave eq PDFs.. try that shit.

The JEE would be more of a challenge. JEE Computer Science PhDs with American MD, and astronauts, I think, are more of an accomplishment. The ones I've met talk about the stories of the JEE test process don't brag about nothingburgers.
I think he more or less gave up when he realized he needed a bus width of 38000 bits.
The successful Venus landers had operational lives on the ground ranging from 23 minutes to 2 hours. Months would have been phenomenal successes.

https://en.wikipedia.org/wiki/Venera
Slackware was my first distro (and The first distro AFAIK) but it always felt rather exotic and unpolished. I use Manjaro now - it feels very compatible with everything out of the box, very polished and reasonably fresh, kind of a luxury var that has everything you would imagine and everything works almost flawlessly. Yet it doesn't give the satisfactory feeling of actually groking your system and having it under almost full control which I had with DOS while FreeBSD was very close to that.
A real-world example from my previous job. You have a chat in your mobile app. Messages are sent using HTTP requests, and received using HTTP long polling. Now imagine sending a message over a slow network while on a departing subway train (service is only at stations). TCP & SSL are established successfully, then the request itself is sent, but you leave the network coverage before you receive the response. So you have no idea whether the message was actually sent. When you reconnect at the next station, you receive a message over long poll, but — because the request failed as far as you're concerned — you have no idea whether it's the message you sent. To resolve this, you need to have the ability to ask the server for a response to a previous request, but without actually performing that request a second time. Or, alternatively in this particular case, you need the server to accept a unique client-generated ID in the request and return it to you over long poll.
Amazon Web Services Buys Encrypted Messaging Service Wickr
The perf difference was due to the compiler being able to infer 'const' by way of 'static'.

Advocating 'static' when your actual intent is 'const' does less experienced readers a disservice; they will assume that 'static' is meant to make things faster, and be disappointed when it doesn't work for non-constant values.
Providing 'idempotency' in this case commonly means to be robust against transient network partitions and timing delays. This goal can be met efficiently with a timebound nonce. (Indeed that is a common approach).

A request identifier is a much stronger and user visible property to your API. Where an 'idempotency' key is used simply to prevent replays, a request identifier is a property that a backend needs to store, index and serve queries against for a much longer period of time. Furthermore this data must be client generated by definition which would require some namespacing mechanism to keep the data model logically correct. Alternatively, just give me a random number (as this rfc suggests).
While this is fun to use, it was kind of meaningless before Linux did their huge powers refactoring a few years back.

As it turns out, turning off unused peripherals like HDMI and ethernet save you more battery than any tweaks you can do.

Anyway, around Linux 5.00 my old laptops battery life went from 2-3 hours to 6-7 and I haven't touched powertop since then.
Everything depends on the city, but in my experience it's de novo. Code changes every 3 years (usually pretty minor stuff). Additionally every site has unique features. Different shape, different elevations, different neighbors, different soils, etc so some rework of the plans is always necessary to accommodate those differences.
What have we learned? Don't use C++
Your links say that program synthesis in general is the holy grail of computer science etc, you said that the holy grail is "program synthesis from informal spec" and by that you meant a natural language specification as per the context of our conversation so far. Are you now trying to subtly shift the goalposts?

If so, please leave them alone. You have no reason to assume that program synthesis from a natural language specification is "the holy grail" of anything. But I'm glad that our conversation at least made you look up a few links, even if only to try and win the internet conversation from what it looks like.

So what did you learn, from what you read about program synthesis? Can you see why your assumptions earlier on, about "narrow use cases" and the like were wrong?

Edit: btw, the Freuder paper you linked is about constraint prorgamming, not program synthesis.

And did you notice that one of your links above is the abstract of the review paper I proposed you read, earlier?
Tribes.
Given how Ray "provides [...] exactly-once semantics" for its actors, you could draw similarities between it and workflow-as-code frameworks such as https://temporal.io. The way that Ray splits up actors and tasks looks similar to Temporal's Workflows + Activities split: Workflows (Ray actors) contain orchestration logic and have their method calls/results durably logged. Activities (Ray tasks) perform the expensive computations and any interaction with external systems and are not durably logged.

If you're in the .NET ecosystem or interested in distributed systems in general, you may like Orleans (https://github.com/dotnet/orleans), which I work on at Microsoft. Orleans contributes the Virtual Actor model which other modern actor frameworks are starting to adopt since it is well suited for the hectic, failure-prone environment of distributed systems (which those so-called Cloud Native Apps live in). The Ray paper linked from the article (https://www.usenix.org/system/files/osdi18-moritz.pdf) discusses some similarities. Slight correction on the paper: it states that "For message delivery, Orleans provides at-least-once [...] semantics". It's at-most-once. At-least-once messaging semantics (usually implemented via automatic retries) aren't ideal for these kinds of systems, in my opinion.
nah. its not even clear these days. people disappear and next time they are "killed in an encounter".
https://thekashmirwalla.com/2021/07/in-kulgam-gunfight-famil...

just a few days ago this kid was killed, heck his throat was first slit. the police say he joined militancy on 18th june but locals say he played cricket and scored runs on 28th of june so who knows.

then you have multiple times when the army and the police was found to have conducted fake encounters where they killed innocent civilians in the name of getting prize money.

few week ago there was the grenade attack in srinagar but that was immediately after the all party meeting with the drone attack that caused another stir.locals belive these are diversionary tactics.
Yes, that is what I meant by my initial post. “You are the company you keep” is one of the most true sayings, in my opinion. Unfortunately (and fortunately) that includes the parents and family one is born into.

If you are lucky enough to have parents that sparingly eat Doritos or soda and do not keep it in the house, I assume that it will have a greater likelihood of rubbing off on the children.
In the near future: Microsoft acquires Figma and creates CoDesigner
In the near future: Microsoft acquires Figma and creates first CoDesigner. This will be the tech founders dream. No designers needed. No problems in implementation. Start from proven dataset, check sentiment results, check accessibility, etc. On a serious note: Did you know about AI based design tools? I am prepared for this eventuality, already thinking about self sustained life.
Best Gaming Keyboards for 2021
Hayek did not, actually. His argument for it can't work but it can work using markets assumes P=NP and that humans are capable of running algorithms that computers can't, but only when they act as perfectly self interested rational actors.
Depending on one's definition of "your PC", they do sell "local" TPUs: https://coral.ai/products/accelerator
" Change a few lines in an afternoon? Nobody cares about the history."

If you changed a couple lines of code as part of a module refactor or something i.e. ongoing changes, then sure.

But if you were fixing a bug or doing some very specific thing, those are actually the times where hyper-specific contextual commits are necessary.

Git is this generic tool for which we still have not yet learned all the best practices and idiomatic usages.

Probably there should be a handful of types of commits, not more than 3-5 i.e. 'change' 'bug fix' 'upgrade' 'internal release' 'major release' (these are probably bad examples).
> the OSI getting to unilaterally define the technical definition of "open source" being controversial even within the software engineering community

I don't think this is controversial? The OSI defined the term when they introduced it, in the late 90s. When Microsoft came out with "shared source" there was a huge amount of pushback from people saying "don't think that this is open source" (ex: https://www.linuxjournal.com/article/5496)

> Copilot doesn't only pick up "open source" code... it picks up any code that has been published under any reason

I agree. I'm not defending Copilot, and I think the legal questions here are interesting and tricky. My pushback here and throughout this page has been when people say non-commercial licenses are open source -- this thread started with kuon saying "I have a lot of open source code that I love to share for things like education or private stuff, but if you want to use it for something real, you need to hire me"
This might sound rude and doesn't add much to the conversation, but this issue can't be fixed unless you "fix" people.

We can be eloquent, humanitarian, calm and polite, but the reality is that we can also be cruel, vindictive little animals that seek out to ruin everyone's day. There is no fixing social media because our nature doesn't allow it, and you can fix the business aspect, but not how the users utilize it, unless you restrict them to the point we can't call it a social media platform anymore.

TL:DR Fixing human nature isn't going to happen. The more popular a platform is, the more positive and negative voices you'll have in the platform, and we all know that we linger and give more attention to the negative more so than the positive.
It's out of your way if you so desire, just squash and commit. What you pay the price for isn't satisfying git's whims; it's a better debugging or learning experience months or years down the line, which is something that git enables you to do.
It's not just training data going into the result, the user is responsible for prompting and picking correct formulations, or fixing or discarding. So it's still semi-manual work. It's just Copilot, not yet full Pilot. The copyright should belong to the human assuming they could have written the same code if they had access to search the internet for help. So it works like a search engine when it's replicating verbatim. Should be considered similar to coding with access to internet for answers.
Malformed Wi-Fi name bug can require iPhone factory reset to fix
This reminds me of Bootstrap Studio for build UI for boostrap, that is around $60 for lifetime access but saves lots of time. I will buy this when my next bootstrap project starts.
I agree with that, but it seems like the use case specified is ordinary power conservation mode, not critical, thermally-induced power reduction mode.

And also, why are systems shipped with inadequate thermal control?
It matters that the client knows the server is offering idempotency, because then the client can safely do things like re-try a request if it didn't get confirmation -- at least I think this makes that possible? It is suprising to me the standard doesn't mention it though, so maybe I'm missing the boat?

If a client just knows it provided a "request-id", but not that the server provides idempotent semantics, the client can not safely re-try a request in which confirmation was not retrieved.

Or, you know how when you click the back button and see that message "this was the result of a POST request, but we can't actualy show you the response" -- because the response wasn't cacheable/cached, and the client can't safely re-do the request to get a new response, because the request was not idempotent.

The client knowning the request is idempotent avoids all sort of inconvenient (and sometimes confusing) client/user-agent behavior. For both ordinary human-readable HTML, and APIs (although by being an HTTP header, I guess this standard is only about API's as a use case?). Just knowing "we supplied a request-id we don't know what the server plans to do with it" is not sufficient. This is why HTTP distinguishes between methods that are idempotent and not -- which just means methods that it's, by the standard, the server's obligation to implement as idempotent. This is a way of making any method opt-in idempotent.

I think?
For me, as consumer it's just another option of something to eat, which hasn't lived like an animal. The 'cultured' in meat implies a technological process whose internals and details I don't really care about. Tofu, Tempe, cultured, whatever, doesn't matter to me. Until it lands on my plate it has gone through most of the same industrial, logistical and commercial channels as everything else which lands there.
I actually don’t trust Google with the documents. In many cases they contain more valuable information about new ideas and directions for products than my email.

My goal would be to move completely away from Google. I have no problem going all in on Apple.

I’ve tried Microsoft office’s solution and it’s so messy with its weird domains and logins, attempts to work w the installed apps. I’m looking for non-infiltrated versions of the gsuite apps.
@devops000 thanks for your comment. Stay tune.. we will release those features in our next UI kit blocks "E-com" :)
Sounds like the marketing department participated in writing the docs this time.
I thought it interesting to think about too. Because we measure everything using short-term values, we don't understand what we do to the long-term future.

We could, but we don't seem to readily learn from past similar situations.

Ideally the container would serve its purpose for as long as needed and breaks down accordingly - there's a high level of variance though, and our ability to refrigerate extends that. So because the expected 'lifetime' of a perishable good transported in plastic is highly variable, its not a simple time-matching problem.

Who knows - maybe our dumped plastics become compressed into the future equivalent of diamonds...?

But yeah, humanity generally has a way of finding workarounds / treatments etc. etc. For some reason I was recently reading wikipedia about how "Anodizing was first used on an industrial scale in 1923 to protect Duralumin seaplane parts from corrosion" and now its commonplace, extending durability everywhere.
When the people making the decisions actually know about the things they're deciding on, democracy can work great. When the decisions are made by people who know nothing about the topic but are totally convinced they know everything about it no matter how completely wrong they may be and no matter how many provable facts you face them with, democracy fails utterly.
Seems like a tail wag. The header is in common use in APIs in the wild, so IETF wants to formalize it.

Not unreasonable, but doesn't seem to add much value either.

With standardization, load balancers or reverse proxies could add a limited idempotency guarantee to reduce the load/implementation cost on the application layer. I don't think anyone is asking for this though, nor do I think they should be...but maybe I'm wrong about that. "Free (quasi) idempotency for small environments" could be a feature.
I wonder if it is more that users are addicted to twitter or facebook than they like the services. Or if it is more a thing of everbody else is on there.

I am confident if a free simple social network had caught on among college users about the time wikipedia started then facebook or myspace never would have been commercially viable.

Almost all users prefer no ads and privacy to ads and no privacy.

I disagree that that experience needs to be expensive to deliver. Imagine a decentralised social media network hosted on its users compute devices, kind of like email used to be. Aside from large streaming videos not that much processing power or storage is required per user.
In addition to Boyd and Vandenberghe, I like "Lectures on Modern Convex Optimization" by Ben-Tal and Nemirovski. Particularly the section comparing linear and conic optimization problems.
Not really. PRs have become the new commits. I only pay attention to the changed files tab in GH. I encourage other people to commit early and often and share their progress with the rest of the team.
I work a strict 40 hour work week, but I hardly know anybody else who works that much in my social group in the Netherlands. 32 is far more common; I think only about 4 of the 80 people in the company I work for work the full 40. I only work this much because my wife is jobless.

So it's strange to see it described as the low end of the scale. I'd pick 24 hours per week.
Funny enough I did a bunch of projects that required pushing like 16K output (video wall, not a personal setup) and at that point Windows becomes the only option because it requires high end GPU and an array of outputs.
That was a bit edgey, but I have seen far too many devs recreate OIDC using JWT. Writing their own token parsing and validation. Doing their own token expiration handling.

These days, just use OIDC. It takes care of everything for you. Most of the time, you just point your OIDC library at your auth server URL and it handles everything.
If you don't catch speeders, you up the risk of speeders causing a vehicular crash, which can lead to injury or death for you and me. Legislative branches passed laws around maximum vehicle speed, cops enforce that as a deterrent. It's for all of us, not the waste of time you seem to be suggesting?

I was in Texas recently and saw first hand what it looks like when police enforce 0 traffic laws. It ain't pretty.
Why the Rich and Educated Always Stacks Ethereum (ETH) and Ripple (XRP)
I think there’s some truth to this. To me it seems like the social media amplification and pile ons take it to another level though.
I think you missed the part where he states:

> that could could[sic] get nowhere but there, and lawyers could prove it

Also, the letters in this case are not representative of the creative work itself. If you used the title font to write your post (hypothetically, I know HN does not allow this), you'd be in bad water already.
HN markup(sic) is just beyond dumb (and your edit window has likely expired) but in the future you'll want to indent preformatted things by 4 spaces because the backticks are unconditionally ignored

Ironically, view-source on your comment still had the correct line layout, although it seems to have eaten the intra-element spacing, so:

┌─────┐
│←┤
││(◣◡)│
│└─◡◢┘
│─┆┌─◢┌─┈┐
││││(|)││
│││(O)││
│└─└─┘─┘──┐
│└─└─┘─└─┘
│└─└─┘─└─┘
│└─└─┘─└─┘
└─└─┘─└─┘
It’s arguable that many existing branches should be consolidated into Homo sapiens including Neanderthals and Denisovans based on generic information.

https://en.wikipedia.org/wiki/Interbreeding_between_archaic_...

As such the lumpers have real support based on current generic information. Anatomically distinct branches aren’t enough to declare something a different species.

Discovery however favors splitters as prestige follows from discovery of new branches of humanity.
Indeed; Umberto Eco dramatized this phenomenon in Foucault's Pendulum (even before the related Poe's Law was formulated).

> People [...] sense instinctively that the [...] truths [...] don’t go together, that [the promoter is] not being logical, that [they're] not speaking in good faith. But they’ve been told that God is mysterious, unfathomable, so to them incoherence is the closest thing to God.

This tangles up with the appeal of being an "initiate", "on the inside", and knowing the secret truth, and the combination is powerful.
> Limited human lifespans are directly related to the successor problem of monarchies or dictatorships and are a major reason why democracies are more stable.

Given how long some monarchies have been around and how quickly some democracies fall to extremism that would actually be interesting to compare.
It’s worth looking at primary sources for “Holodomor”, a depressing amount are from Ukrainian fascists.

The consensus among historians is that there was indeed a famine, one of the periodic environmental ones in the region. Planning was indeed slow to react to the famine and the sabotage by landlords, so food aid arrived late.

It was also the last famine in the region. The landlords that destroyed food were expropriated, land was collectivised and agriculture was industrialised. Talk to any older Ukrainians and they’ll tell you there was plenty of food throughout their lifetimes until the 90s after the USSR was defeated.
Yeah. That's the problem itself.
>It’s clear based on user behavior that users like the experience that centralized, for-profit social media networks provide.

I don't think this is a given, and it's not that expensive to deliver either - the problem is more with the de facto monopoly of network position. But there are lags on all these kinds of activities, and user behaviour today, is conditioned on user experience yesterday, it may not predict well user behaviour in the future. Social media is still new, the experience of having it delivered to a mobile phone barely 10 years out of the box for most of the world.

Consider a marketing team that predicted the future of the book by looking only at input from the reading habits of a kindergarten, and ignoring any correlation with how those would change as the kids got older. Note that none of this has anything to do with payment per se, and neither does today's social "advertising enabled" media.