skysight-inc/HackerNews huggingface dataset:
Part of that is because they have to other wise the building would collapse on its own.

A big issue people don't talk about is that a lot of the concrete China makes is subpar and not up to spec by US or EU standards - they don't use the right (aka more expensive) grade of sand, so the concrete doesn't bind as strongly as it should. The sand used to make concrete has to have rough edges, something about the surface area, which ironically means that desert sands aren't very useful - they've been rounded by wind erosion and rubbing against other sand grains.
idk about rapist, seems more like he was just really into bdsm and exhibitionism, but the nearest town from where he got taken by the ocean is pretty famous for prostitution.

REALLY weird seeing some of these posts where he has girls in the full nude with things up orfices in like the area I live in. It's all I'm going to be able to see walking past that corner now
I assume that there were two completely different CMLisp/StarLisp implementations as the language described by Hillis' disertation and StarLisp paper (ie. with xexctors and xaps) is significantly different in the overall design from the StarLisp as described in CM-2 manuals and as implemented by the Common Lisp CM SDK (it can be found somewhere on the internet and works in SBCL). The newer version is significantly lower-level and does not have the xector concept (and its design is similar to C and Fortran APIs for CM). I feel that the reason for this change was to make collective communication operations more explicit, probably because the store-and-forward communication network of CM-1/2 isn't exactly fast at doing arbitrary global permutations.
I suppose you know this, but green means the account is new (https://news.ycombinator.com/newsfaq.html). Angry people sometimes create new accounts to vent. That's not a good use of HN, but let's not respond as if there's something wrong with new users coming to the community. We don't want this place to become insular and brackish. New users are the community's freshwater!
If I put a section in my LICENSE.txt prohibiting use as training data in commercial models, would that be sufficient to keep my code out of models like this?
Came here to mention that I thought Christensen was absent from the list, but thought your Ecclesiastes (which can be found in just about every Jewish or Christian Bible) recommendation was inspired.

Ecclesiastes talks so much about the rhythms of life and the benefits of gaining knowledge and then using knowledge, the benefits of working hard and celebrating accomplishment. When I look at our various economic cycles, especially periods of innovation followed by periods of consolidation in tech, I can see a lot to draw from Ecclesiastes. I'll be pondering it more!
If "modern" means fast, then no. If "modern" means what people are using in 2021, then possibly.
I respectfully disagree. If you take 15 min to understand the basics it becomes trivially easy and the productivity you gain going forward is massive.
Except the problem with your theory is that Bret doesn't make content related to conspiracy theories...
How Covid-19 Is Changing the Healthcare World
I'm not quite old enough to remember: when high level languages like C gained wide adoption, how much pushback was there from the philosophy that if you're not writing it in assembly, you're not really writing code?
Established folk with a track record and a seemingly good idea can just look around and find investors willing to throw in millions of dollars. I've seen it happen a couple times myself.
This is where microsoft's billion dollars went in OpenAI.
Clever
> I'm not sure what you mean by that? querySelectorAll returns an iterable.

Apparently my knowledge is outdated. Last time I tried to switch from jQuery to vanilla JS, the results of document.getElementsByTagName and others were not iterable with for-of.
Thanks! That's a great suggestion. I forgot that was in there.

I read Mythical Man Month many years ago and enjoyed it. Time for a re-read. Of course it won't cover the third wave very well though. Would love to see a blog post cover that.
I'd expect those ISPs to use jumbo frames only where they use PPPoE so that it looks "transparent" to non-PPPoE traffic.
(I hate to be that guy but a flywheel is an energy storage device, not a positive feedback loop.)
The utility and quality of this will likely depend on language use:

https://madnight.github.io/githut/#/pull_requests/2021/1
You shouldn't be allowed to touch computers.
The lisp dialect (*Lisp) did get off the ground. I programmed in it.
I prefer the wingman

https://haskellwingman.dev/
I'm not sure how to express my reaction to this kind of design/architecture without being rude. Especially with performant open source databases being available. Was this some sort embedded app or toy project?
I'd argue that Svelte is easier for beginners or simple stuffs, the tutorial is miles better than react's.

But of course, for complex stuffs, react's bigger community becomes to the rescue with many edge-cases solutions
So, if they have a captive portal, why not put the menu there before you login? That would even make the QR code a moot point, scan QR code or just connect to the wifi and menu magically appears…
Download or get a textbook and read it yourself + find some lectures on YouTube with a high rank that you also feel you are getting something from. This is and always has been the best way to learn most subjects.
This is a lovely analogy, akin to "sharing mix tapes" vs "sharing MP3s on Napster". I fear the coming world with extensive public camera surveilance and facial recognition! (For any other "tin foil hatters" out there, cue the trailer for Minority Report.)
Strange framing. Working very hard in the US has made my compensation increase 7X in 9 years. I’m not capital (this isn’t a static group, btw), I don’t feel exploited, and I don’t exploit anyone - I invested in myself and successfully optimized for long-run outcomes.
> So everything generated also GPLv2?

Almost certainly not everything.

But possibly things that were spit out verbatim from the training set, which the FAQ mentions does happen about .1% of the time [1]. Another comment in this thread indicated that the model outputs something that's verbatim usable about 10% of the time. So, taking those two numbers together, if you're using a whole generated function verbatim, a bit of caveat emptor re: licensing might not be the worst idea. At least until the origin tracker mentioned in the FAQ becomes available.

[1] https://docs.github.com/en/early-access/github/copilot/resea...

[2] "GitHub Copilot is a code synthesizer, not a search engine: the vast majority of the code that it suggests is uniquely generated and has never been seen before. We found that about 0.1% of the time, the suggestion may contain some snippets that are verbatim from the training set. Here is an in-depth study on the model’s behavior. Many of these cases happen when you don’t provide sufficient context (in particular, when editing an empty file), or when there is a common, perhaps even universal, solution to the problem. We are building an origin tracker to help detect the rare instances of code that is repeated from the training set, to help you make good real-time decisions about GitHub Copilot’s suggestions."
Would i be able to use something like this in the near future to produce a proprietary linux kernel?
> The DX is so good that building things is incredibly fun, intuitive, and headache free. I can’t emphasize enough how empowering it is.

Yes! I've been a full-time React developer for about 5 years, and recently had the chance to try Svelte on a small pet project. I'd written most of the project in React and had a free weekend so I figured what the heck – let's see how it'd look in Svelte. :)

Within a day most of the functionality was in place, and the code just felt _beautiful_. I loved that it removed so much boilerplate (wrote some examples here[0]), and some of the React headaches (like using "Undo" in a controlled <textarea>) were just gone. The ergonomics (especially the built-in stores, error handling, and <svelte:head>) were lovely surprises!

I'm really bullish on it and so happy it's starting to grow.

[0]: https://mtm.dev/react-vs-svelte
Extending Booleans to Enums
Did you watch the episode with Dr. Kory and, if so, what are your objections on what was being said?

Note that as far as I can tell and remember, YouTube policy at that time was that content not in line with health authorities was not allowed, but since then Ivermectin was explicitly added (I might be wrong, that's just what I remember when I looked it up).
> At $1mm you really are independently wealthy in most cases.

This doesn't strike me as true. A big facet to consider also is liquidity. Are you talking about $1M in net worth? If so, I disagree with you: a big chunk of that $1M is likely very illiquid for a younger person, tied up in a house and retirement accounts with penalties for withdrawal. But sure, if you have managed to save $1M above and beyond equity in your home and tax advantaged retirement accounts, then you are probably independently wealthy (but your actual net worth is probably significantly higher than $1M).
Unless you're a funeral director
i'm a former physicist but yeah, a few stellar masses worth of energy is beyond (my) imagination

1. always wondered the same. i'd suspect that for most astronomical BH you would first need to worry of X/gamma rays. you could possibly hear a loud chirp since it is audio frequency.

2. the warping of space time here on earth is actually mostly a warping of time, which is even weirder. i means that the time at your feet is flowing slower that where you're head is. about one second on your entire life. that's actually WHY you feel earth gravity.

3. yes, more space is created out of nothing! because there's a vacuum energy density that inflate the local patch of universe.

funnily why all of the above is hard to understand for our human brains, it all makes sense in the mathematics..

i highly recommend the YT channel PBS Space Time for more explanations
Xmovies8 Alternatives (2021) – 9 Best Sites Like Xmovies8
Stack Overflow copt pasta on crack cocaine.
Yes, capital gains taxes would be paid without a Roth IRA. Similarly, if the funds will be used prior to 59 1/2 from within a Roth IRA, then capital gains will still be paid. If there is an early withdrawl, then there is an additional tax penalty. An IRA protects the owner from capital gains, because the funds aren't being used.

I think the point is that the Roth IRA was used in the exact way it was designed and how anyone can use one.
Now put those in a car and I will be interested in an electronic vehicle. 23 million miles on a charge and at night you can use it to power your house.
Tell that to my cpu when using the new reddit
Read the spec
If you restrict yourself using scalafix [1](a linter), scalazzi [2](a linter) or wartremover [3](another linter), you can prevent your code from returning `Any`, `AnyRef`, `Nothing`, or `Unit` and prevent yourself from using `Throw` , partial std lib functions,
or `NonUnitStatements` without explicit annotation.

This effectively locks you into writing pure code (you can extend the linter to cover other things like not using `Future` or not using Java libs outside of `MonadError` from cats[4]). The linters operate on typed ASTs at compile time, and have plugins for the most popular scala build tools. Coupled with `-XFatalWarnings', you can guarantee that nothing unexpected happens unless you explicitly pop the escape hatch, for the most part.

You can still bring in external libraries that haven't been compiled with these safties in place, so you aren't completely safe, but if you use ZIO[5]/Typelevel[6] libraries you can be reasonably assured of referentially transparent code in practice.

There are three schools of thought, roughly, in the scala community towards the depth of using the type system and linters to provide guarantees and capabilities, currently:

1) Don't attempt to do this, it makes the barrier to entry to high for Scala juniors. I don't understand this argument - you want to allow runtime footguns you could easily prevent at compile time because the verifiable techniques take time to learn? Why did you even choose to use a typesafe language and pay the compilation time penalty that comes with it?

2) Abstract everything to the smallest possible dependency interface, including effects (code to an effect runtime, F[_] that implements the methods your code needs to run - if you handle errors, F implements MonadError, if you output do concurrent things, F implements Concurrent, etc.) and you extend the effect with your own services using tagless final or free.

3) You still use effect wrappers, but you bind the whole project always to use a concrete effect type, avoiding event abstraction, thus making it easier to code, and limiting footguns to a very particular subset (mainly threadpool providers and unsafeRun or equivalent being called eagerly in the internals of applications).

My opinion is that smallest interface with effect guarantees (#2) is best for very large, long maintenance window apps where thechoice of effect runtime might change(app), or is out of the devs' control (lib); and #3 is best for small apps.

TL/DR; You can go a really, really long way to guaranteeing effects don't run in user code in scala. Not all the way like Haskell, but far enough that it's painful to code without conforming to referential transparency.

1. https://github.com/scalacenter/scalafix

2. https://github.com/scalaz/scalazzi

3. http://www.wartremover.org/

4. https://typelevel.org/cats/api/cats/MonadError.html

5. https://zio.dev/

6. https://typelevel.org/
How is it different from the status quo of people just doing the wrong thing or copy pasting bad code? Yes there's the whole discussion below about float currency values, but I could very well see the opposite happening too, where this thing recommends better code that the person would've written otherwise.
> - under what license the generated code falls under?

Is it even copyrighted? Generally my understand is that to be copyrightable it has to be the output of a human creative process, this doesn't seem to qualify (I am not a lawyer).

See also, monkeys can't hold copyright: https://en.wikipedia.org/wiki/Monkey_selfie_copyright_disput...
> ordering and payment is done via the web browser

This still assumes each customer has a phone. I bought an LTE watch so I could leave the distraction of my phone behind while I dine.
https://twitter.com/fravizza/status/1409690047662592003?s=20
That's all great until you have to use your retirement funds for medical emergencies.
At least in openSUSE, we always build with gcc -g and then later strip debug symbols into separate debuginfo files. This leaves a unique hash in the original file and that makes them vary if the build path changes.
My personal take is working hard is a precondition towards being successful but not necessarily a guarantee.

Lots of normal people work very hard, many normal people I know outside of tech are working night shifts and a day job to just sustain their lives. Many of these people rarely have a full day off, rather they might scale back the night job in order to get rest, or rest whenever their scheduling allows for it. There probably working just as hard as a Bill Gates, but these people aren't exactly walking towards a path of riches. They're just sustaining and it's a very unfortunate reality of America today.

Really success comes from the prerequisite of hard work, the aptitude of the individual in regards to the task, and the ability of the resulting work to pay off in convexity, similar to a call option in finance. Generally non-convex pay outs are also associated with risk, perhaps alot of it. So really success comes from working very hard, being smart about it and taking on risk.
To the metadata servers? They presumably hold keys to access all kinds of backend systems anyway. The certs don't require any additional trust. There must already be infrastructure in place for deploying said keys.
How Two Startups Made a Fortune in Fees on PPP Loans
What interests me most about the development of tools like this is how it might go on to influence the evolution of programming languages. The article that was posted on the CompCert verified C-compiler for instance. What if machine learning could make the cost of developing using more programming languages with stronger guarantees (ie rust, coq, etc) easier? Using languages with more internal checks could also help manage risk the the co-pilot gave a buggy/insecure suggestion.
How common is it now for a hardware button that isn't just dedicated input for software?
I read a book on authors work habits and this pattern seems very common. Work for a relatively short period in the morning (by modern work standards) then spend the rest of the day at leisure.
Sure. There are definitely colleagues I would recommend over others if I had to only choose one, but I don't. Bouncing between large companies means "sure, I'll refer you and get $5k for doing so" as long as I think you can pass the interview.
Yes, Tim Ferris tells us we should work harder to have what he has.

Next time, I will be sure to be born in the Hamptons. He made the right first choice.
Why adding to the title [dupe] ?
Hijacking the World: The Dark Side of Microsoft [pdf]
From what I recall, the 1500 number was chosen to minimize the time wasted in the case of a collision. Collisions could happen on the original links because instead of point-to-point links like we have today, they all used the same shared channel. (This was in the days of hubs, before switches existed.) The CSMA (Carrier Sense, Multiple Access) algorithm would not transmit while another node was using the channel, then it would refrain from transmitting by a random length of time before sending. If two nodes began transmitting at the same time, a collision would occur and the Ethernet frames would be lost. Error detection and correction (if used) occurs at higher layers. So if a collision occurred with a 1500 byte MTU at 10Mbps, 1.2mS of time would be wasted. IIRC, the 1500 byte MTU was selected empirically.

Another reason for the short MTU was the accuracy of the crystal oscillator on each Ethernet card. I believe 10-Base Ethernet used bi-phase/Manchester encoding, but instead of recovering the clock from the data and using it to shift the bits in to the receiver, the cheap hardware would just assume that everything was in sync. So if any crystal oscillator was off by more than 0.12%, the final bits of the frame would be corrupted.

I've actually encountered Ethernet cards that had this problem. They would work fine with short frames, but then hang forever once a long one came across the wire. The first one I saw was a pain to troubleshoot. I could telnet into a host without trouble, but as soon as I typed 'ls', the session would hang. The ARP, SYN/ACK and Telnet login exchanges were small frames, but as soon as I requested the directory listing, the remote end sent frames at max MTU and they were never received. They would be perpetually re-tried and perpetually fail because of the frequency error of the oscillator in the (3C509) NIC.
It is not just the quarter result, the managers also are evaluated based on what they did the last few months. If they miss their projects for the quarter there is no promotion, no pay raise.
Just curious, did you have remote (WAN) access set up?

I have one of these at my parents house, I had them unplug it, once I read this, but I was always wary of turning on remote access, as in it would only be accessible from the LAN, I haven't had a chance to go back in and check if it was hit, but I'd like to think that without remote access turned on it wasn't vulnerable.
>most developers can write code a lot faster than they can verify it

what? so people just write code and never read it back?
I doubt people have the capacity to care like that. I mean, humans as species. What's able to salvage this is good regulation.
This should not be flagged. Bret and Heather both have PhD's in biology and the episode in question with Dr. Kory also featured Dr. Malone the inventor of mRNA vaccine technology. This is science not politics.
I agree with this viewpoint.

A tool which increases how rapidly we can output code—correct code—would allow for more time spent on hard tasks.

I can see the quality of some "commodity" software increasing as a result of tools in this realm.
It seems to replace/shorten the loop of “Google for snippet that does X” copy, paste, tweak, no? Which of course is super cool for many tasks!
"Why can’t we use carbon fiber or aluminum or anything that won’t rust?"

You can. Stainless steel rebar is a thing and would, largely, solve the problem of spalling due to rusting steel reinforcements.

As you can imagine, stainless steel rebar adds a significant cost.
Has Walmart entered that market yet?
It is even entirely possible that this approach hits a middle-ground that serves the corporate software-development space better than highly-flexible languages.

The difficulty with high flexibility is that the expressions become very domain-specific very quickly, creating the challenge of learning the new abstractions. So one isn't just a LISP developer, one knows how to write in the specific forest of macros that have been built up around one specific problem domain. The end result is code that means nothing to a reader who doesn't have a dense forest of macro definitions in their brain (at least in this era, their IDE will likely helpfully pull up the macro definitions with a mouse-over or cursor-over gesture!).

Contrast with this approach, where the complexity of abstraction is being baked into the lower-flexibility language. The code is less dense, and that's a tradeoff... But grab any 10 developers off the street with experience in that language and have them read it and 8 of them will likely be able to tell you with some accuracy what the code is doing. Not a trick I've seen possible with even very experienced LISP developers on a codebase they've never seen before.

... and, of course, being able to grab a random 10 developers off the street and have 8 of them up-to-speed in no time at all is crack cocaine to big businesses with large and complex systems maintained by dozens, hundreds, or thousands of people.
I've heard that there are people who think in words, and those who think in pictures, and combinations of the above. If you don't think in pictures, cannot visualize what you will paint, what's your point of reference enabling you to put paint to canvas?
> Just look at what your average person is able to accomplish with Excel.

Approximately nothing.

The average knowledge worker somewhat more, but lots of them are at the level of “I can consume a pivot table someone else set up”.

Sure, there are highly-productive, highly-skilled excel users that aren't traditional developers that can build great things, but they aren’t “your average person”.
How do you opt out your own GitHub repositories from being a part of the training data?
It has subsequently been discovered that another group of crustaceans, the mantis shrimp, contains species whose club-like forelimbs can strike so quickly and with such force as to induce sonoluminescent cavitation bubbles upon impact.

More on the Mantis Shrimp (including super-color sight):
https://theoatmeal.com/comics/mantis_shrimp
>Whereas when you're reading code for correctness, you're just following the logic that's already there. If it works, it works. How could it possibly take longer than the whole creative process of coming up with it...?

That's exactly the problem. If you "just follow the logic" you can miss important details or edge cases that you would be forced to deal with by coding it yourself.

I wouldn't mind using something like this for mundane tasks, but I would be very careful with these tools while developing high performance code intended to run on specific hardware.
I tried TabNine and it wasn’t a huge improvement because what costs the most time isn’t typing stuff but thinking about what to type.