skysight-inc/HackerNews huggingface dataset:
Yes, I agree that is the point of building a product. The one catch there, is when you have a client paying for development there are compromises and time to market considerations to which can affect having a product available to the wider audience.

In our case, we were working both with the client we were building the product for initially and also we had prospected a number of other clients and were trying to get an MVP out that solved the problem and then iterate. However, that didn't work for the primary client and a number of things he wanted in his MVP were not good general product market fit, which made it harder for us to manage the timing & expectations. So while it was overall less expensive initially out of my pocket, the timeline was dictated/dominated by the client and special features they needed which took away from making a generic product that we could've had in the hands of others faster. Which in the end meant we had more product/development churn then if we had gotten the more generic 80% MVP out for a wider audience.

That's what I meant by we could've focused on general product first.
Big ol’ “Citation Needed” on this one.

The flip-side here is that a language that doesn’t support basic programming language theory concepts dooms its users to repeat the mistakes of those who discovered them.

I also would personally disagree that any statically types language without generic types and without non-nullability (e.g. `Option`/`Maybe` and `Result`/`Either`) is severely lacking in the ability to express programs that are easy to understand.
nice

Does this mean keeping all status up to date in Jira? would you mind sharing how you do this?
Product success via pure advertising volume, is not an effective strategy. Maybe that oversimplification needs work.
I'm sorry to be this negative, but I sincerely believe Scala to be the worst seriously used programming language of modern times. It should just end.
Well, consider the source.
The Pheonix Project and The Unicorn Project are two good audiobooks centred around Devops and Software Development.
Unfortunately it is, you may want to have a look at: https://krausest.github.io/js-framework-benchmark/current.ht...

Filter for wasm frameworks like “Yew”.
Ways for Retargeting: Tips to Increase Sales
I read it for a philosophy class in college. I still remember the moment of genuine shock when, partly though the book, I closed it and noticed "Non-Fiction" written on the spine!
The distinction here is not really interesting. Besides, contacts are content too.
I wish I did this. Your friends only tell you the name of their kids once. If they even remember without you prompting. And then time passes, you have interactions and it's too hard to ask: "hey remember your three year old daughter I've mailed christmas presents for...what's her name again?"
Yeah. Dijkstra is easy. It’s really common around the Hamilton, Ontario area where there’s a large Dutch population.

At least in bastardized Anglo pronounciation it’s always been:
Dike-struh

No idea what it means, though from the context of this thread I’m assuming it has something to do with dykes!
I work in software supporting a field I knew little about (genetics). After 6 months of coding up tools, going to talks and kinda getting the gist, I started taking a couple classes. It really helped my fill in some gaps in my background knowledge and I’d wished I’d done so sooner.

So I think both learning methods have their place.
It optimized for users vs shoppers, which I appreciate because user acquisition can contradict the pursuit of user experience optimization and I am more frequently using a solution than shopping for my next solution.

As for JS, this is a web app.
That's the book review version of those jokes where someone writes to the agony aunt about some relationship drama and the response is all about what might be wrong with their carburetor.
Sounds a bit like they just like to try out new languages.
Reverse Engineering for Petroleum Engineers
And yet, statistically it does.

People not "growing their own food" buy into all kind of food trends, not to mention a whole nation sticking to 30-50 nationwide chains (restaurants, food brands, etc) for the huge majority of their food.

Compared to an American of 70-80 years ago, or a modern French or Italian person this is huge conformism and sheep like consumption. And food is one of the most essential things in our life (not to mention the health implications).

Although this is not about "growing own's own food". You can still buy your own food without modern consumerism, as societies have done since forever in farmers markets, etc (and people still do in other parts of the world), where the food is not mass produced and branded by 10 major chains, nor the restaurant choices are 20-30 nation wide chains.
The motions of the sun and seasons (my personal experience) are much easier explained by the "round" model :) The truth from ground level is more like "I can't actually know if it's round or not, because the scale is invisible from here". I readily admin I have not seen a round earth and can't say that I know for sure (in the end not even my own memory can be trusted, so I can never really know). But even with that the flat model is really horrible.

My point being, I'm sure theres some more weird psychological phenomena that makes people want to believe in a flat earth, rather then hanging out in meat space.
Well what do people suggest that companies like Apple and google do in such a position. They have hired somebody on a work visa and want them to stay after their six years of visa are up. The only option is to file for a green card and one of the requirements of the green card labor process is to show an ad in a local newspaper. So they do what the law tells them to do.
Working outside is great and the author has put considerable amount of effort into making it work for him. Hopefully with computing becoming more ubiquitous, hardware will become more tolerant to the outdoors. For me, our screened in porch works best but still there are only a couple of months per year where doing computer based work outside is viable. The big annoyance here is in the spring when the temperature and humidity are nearly perfect but the pollen count is off the charts. I don't have allergies but also don't want my electronics covered inside and out with a yellowish green blanket of ultra fine particles. Sealed devices that are easily cleaned off would help here but the need for ventilation means most devices can't be sealed.

Our four to six weeks of autumn though... that's spectacular, though I'd much rather hike that time of year than tap away on a keyboard.
>I use Reddit

Stopped reading.
Yes, there are some wonderful people in there. Andy Seaborne has always impressed me with his thoughtful responses. I won't call out any of the bad apples. Usually a question goes something like, "Uh, I'm new to the semantic web and I'd like to do X" and the response is, "this is how it works, you're a dummy and you need to understand how brilliant the semantic web is and you don't need to be doing what you're asking for" or academics who will complain that they're not getting enough credit for providing their brilliant intellectual scaffolding.

Databases, that are run on a shoe string, aren't stable so we're going to make everything federated with linked fragments? Fine, give it a go but you don't need to go on and on about how databases are inadequate because someone isn't willing to foot the AWS bill so they can host dbpedia for ya.

Lets have a go at JSON-LD. RDF/XML is finally recognized as a mistake. A somewhat reasonable mistake because everyone was XML crazy at the time. So what do we do? The exact same thing except this time it's JSON. But it's even worse. We choose a serialization that is prized for its simplicity and we foist the entire RDF stack onto it? Then they claim that JSON-LD isn't about the semantic web so we're good and Jedi mind trick it with, "This isn't the RDF you're looking for".

Because we aren't done overcomplicating simple things we take aim at CSV with CSVW. Granted CSV has some subtle complexities but it's easy and reasonably compact. So now we're going to add metadata to csv files with rdf and then serialize it into JSON as JSON-LD. Great. How do I find this metadata. Either a well known location or in a link header. Whoops I can't publish metadata and reference your csv file. Lets convert your csv fie to rdf. WTF. my 500Mb csv file just became 1.5B triples and it's taking 8hrs. to load it into my triple store!

Don't get me started on people who call themselves ontologists. They're really zombies but instead of eating brains they eat budgets. They should be dispatched the same way, with a shotgun blast to the face. They generally can't justify their decision even though there is a framework to do that, onto clean. I have yet to meet one who even knew what that was. They just convince management that what they're doing is intellectually unattainable by mere developers although they'd be lost without protege, top braid, or excel and what they produce is generally an incomputable pile of garbage. It's always OWL full. "Class or property? Class or Property? Well is is an "is a" relationship."

I'm done writing so I'll just include a list of the half baked ideas that sound good but are a day late and a dollar short. LDP, R2RML, ShEX, SHACL, DCAT, RDF Data Cube, WebID.....

My wife always says to say something nice so I'm going to say SKOS. SKOS is ok.
All the examples include a flight, is there support for local driving trips? Driving an hour is faster/cheaper than plane fare.
See my other comment, this is no different that keeping any other employee around.
Hire an American.
There is an ongoing work on creating Spark alternative in Rust[1][2]. Hopefully, that could help.

[1] https://github.com/rajasekarv/native_spark

[2] https://medium.com/@rajasekar3eg/fastspark-a-new-fast-native...
I think growth is accurate, because growth leads to dominance, and then you re invincible, profit is secured
Absolutely. Black white is also lot more usable in this case than the 'dev edition' white on black.
Anything that loses your scroll position when you click a link and go back is trash.
>A few years of playing every scale and chord progressions in every key back when I was 10 years old, and solfege training with "movable do" and now I can play anything in any key.

"A few years of training", "playing every scale and chord progressions", and "solfege training" is "not a big deal"?

What would be a "big deal" then? Lifelong devotion to play Mary Had A Little Lamb?
A young mathematician refutes a conjecture of 30 years
Thats not a sustainable model though
This is an interesting setup. Do you have pictures or video?
The cognitive burden is inherent in the "training" of the trained player. So whether there's an "additional cognitive burden for a trained player" is a moot point.

This is about reducing the training burden.

And of course the limitations (e.g. of movement between notes, where there's only a single path in the traditional keyboard) are objective and not arguable.
That attempt was does at the interview stage. Nobody wants to hire a foreigner and then spend 6k for their initial H1B, each subsequent renewal and then spend an additional 10k on the green card process.
They need to be paid appropriately and must be absolutely unbiased, also.
What should you know about IIoT?
Umm the Irish Channel is just a neighborhood name. It's not a canal. Yes, thousands of Irish died from yellow fever and malaria while digging canals in New Orleans (Basin St and those going to the lake).

They were considered expendable because they were Catholic (unlike the Scotch Irish who were protestant). They were also lied to and told that New Orleans was close to the Irish communities in New England.
no it just implies the don't willy nilly throw in any feature into the language like Scala, and I am incredibly grateful for it after writing Scala for a couple years, what a mess
And is usually a matter of funding, famously Hagia Sophia was built in five years
> they’ll keep working

You realize that’s entirely the goal of measuring “results vs hours”, right?
While it's just part one, I feel like whether the end result successfully overcomes the problems mentioned is missing. I wonder if in fact it does.

Personally I wouldn't refactor an entire application from scratch unless it was fairly simple. Instead I prefer incremental refactoring and I've found that typescript can be helpful in that regard.
I think it’s the kind of book about which there are several things you could say it’s “really” about, and what you think it’s really about may vary according to circumstances. When I read it as an adult with sons, it felt to me like it was really about his relationship with his son. As such, it now feels to me so deeply sad that I can’t recommend it without qualification.
> People are still totally willing to be part of something like that; people are as haphazard and risky as they ever were.

I think people were much more willing to risk their lives (and risk other people’s lives) in the past than they are today. We have elevated the role of the individual. Younger generations are all “me” generations. (I’m not saying that’s a bad thing, it’s true for me as well.)

Case in point is the Western expectation of acceptable losses due to warfare. If we needed to pull off another D Day invasion, I don’t think we could. Generation Z is not signing up to die in tens of thousands and I don’t blame them. The casualty rates that were once seen as the normal cost of war and industry are totally unacceptable today.
Kotlin wins also because it has a stable and usable Native flavor. Scala Native is a third-party project and seems dead, while Kotlin Native is the core part of the Kotlin language and being developed at a fast pace.
> There are genuine advantages to different technologies

That is also a tired argument. The compile target is WASM. Rust can be the greatest thing ever, but the performance that matters and the only limitations the user will see are those inherent to WASM. Is WASM multithreaded with the execution speed of a Rust binary? No, so who cares?
They look at how their software is being used and the problems people are encountering using it and then decide what is the best path. To roughly quote Rob Pike 'every feature is useful, but they all have a cost, and its about weighing the outcomes'
Our political problems exist on the spectrum of idealism and cynicism, not the spectrum of optimism and pessimism.

Only an idealist would expect such an appeal to have any impact on a system that people have mostly either accepted as inevitable or benefit from.
Thanks, I always appreciate having authors recommended.

I read all kinds of SF regardless of politics and scientific accuracy. I often find authors whose politics I don't agree with give me the most insight into other ways of seeing and understanding the world.

I just love the idea of orbital mechanics, coriolis effects and zero g environments as plot points. I also wish there were SF video games that utilized a mundane SF solar system as a setting.
You still need to go call into Javascript to do any kind of DOM manipulation. The solution I used for wasm-forth (a forth implementation targeting wasm), is to have a js "interpreter", implemented as a single function, that executes a sequence of DOM manipulation instructions, represented as an array of integers. On the forth side, the instructions are generated by a virtual DOM library: as the virtual DOMs are diffed, instead of manipulating the DOM directly it generates a sequence of opcodes to send in one go to the Javascript interpreter.

The cost of the Javascript bridge is minimal: it's a single function call to render or update a whole page, and there is no serialization/deserialization involved since both languages can understand arrays of integers natively.
This is fantastic. Scala 3 is a huge improvement, doing away with main of the pain points of Scala 2 and making using Scala effectively much more straightforward. I'm looking forward to getting to work with Dotty / Scala 3.
Talk about inequality. Faang absorb the bulk of online profits, leaving most websites destitute
What about integers and bitops in 5.3? That seems like a big deal
It may just be this creeping understanding that all you’re going to get is a frustrating surface treatment of any of the concepts contained. As someone well versed in all three, the book gives a light treatment to philosophy, zen, and riding motorcycles.

Honestly I’d have to reread the work for an in the weeds critique, but when I ask the question: “What of it?” I just never had a good answer.

* It may also be that if you approach the book looking for philosophy, wisdom, or zen, then you are doing it just as wrong as approaching the book looking for maintenance advice. That is, it may be a great book, just not of the type someone reading it from a philosophical perspective expects.
I personally don't mind the grunt work and don't consider that abuse. Grunt work is either outright useful or a learning experience.

If blacksmiths were academics they would produce a large number of faulty nails. (One might argue the vast majority would be faulty!) I doubt blacksmiths would find that acceptable, but many (if not most) academics don't seem to care too much about quality as long as the paper passes peer review.

A PhD can become abusive when the advisor wants to produce more work when someone has done more than enough for a PhD. At that point they have a full researcher getting paid only a fraction of what they could be.

PhD students are paid less than apprentices last I checked, too. According to this page apprentices are paid roughly 1/3 of what professionals are paid:

https://smallbusiness.chron.com/apprenticeship-pay-15304.htm...

So far, at no point during my PhD was I ever paid 1/3 of what my advisor is, even if you factor in benefits. I haven't even received a raise (to my knowledge), but he has.

Again, ideally a PhD is like an apprenticeship, but my experience suggests that case is rare.
I love scala, and am very much looking forward to scala 3.

For all the complaints about the language that always pop up in these threads: yes, the language lets you shoot yourself in the foot (with great power comes people who don’t apply it responsibly), but it’s precisely that power that makes it so useful and exceptional when judiciously applied.

I like to say that scala is as if java and ruby had a love child and it all worked out. Unfortunately, that does mean that java people will feel it’s too fast & loose, and the ruby people will feel stymied by its static typing. But I just love that where other statically typed languages generally say “no”, scala says “well, I trust you know what you’re doing...”.

The only substantive tool complaint I have these days isn’t with compiler speed - it chugs through the codebase plenty fast - but with tool startup time. Hopefully the more recent java versions and maybe some native packaging will eventually help with that.
The english "out" is pronounced like the dutch "oud". Would you say "oud" and "uit" are the same? An afslouddijk sounds different from an afsluitdijk. The english "oid" (as in humanoid) I think is closer to our "uit" sound than "out" would be.
> The bit about how when you strip a bolt it becomes your whole project and how you then need to pause and think through all the options before you before proceeding I am sure saved countless hours and dollars to a lot of people.

The bolt here is just used as an analogy for how to address problems in life, balance importance you give to micro vs macro, the beauty and danger that scales up and down in anything, etc.

Sure, it's a smart one, actually useful if taken literally as well, because the writer is very talented.

> The bit about really understanding how the thing works before attempting to repair it is great.

Again, another analogy. The whole book is teaching you how to think. And then go beyond thinking, as an art of living.

Every page is a personal, human lesson. You can stop at the mechanical aspect of it, but it is missing why this is a fantastic writing. It's giving profound advises using a simple, down to earth, vocabulary.

I could have done so with any other gimmick. Just like star wars could have replaced light sabers with something else. It just became an iconic symbol because it's so obviously recognizable and easy to grab.

But of course, they are also good because they chose such an symbology to make it easy to refer to.

You know where you were in class, and the teachers analyzed a book and you though in your head, BS! ZAMM is an exception to that. It is, really, a conscious and deep work of teaching that goes several levels down.
I listened to audio book at age 47, and really had several... moments. Yes. I think there's a lot to be gained from a re-read with some road years on you.
Maybe AcademicTorrents might be used. Is it still a thing?
So this in part comes down to what novelists call a “type of conflict” that Trek makes great use of, but Wars does not. The term is usually “Man vs. Technology conflict” but if I were writing it, I would call it “people versus tools” to clarify that usually fighting off a robot counts as one of the other conflicts. Like if you have to land a plane, that is PvTool conflict.

In Star Wars, this conflict is largely but not entirely absent. In a climactic scene of A New Hope, the rebels get to blow up the Death Star, except—“It didn’t go in. Just impacted on the surface.” Very short bursts in the middle of other conflict. Similarly there is a short moment of Han Solo explaining that he needs to give his computer time to make hyperspace calculations lest they all die—it is another really tiny moment to enhance a larger existing conflict.

Whereas with Trek it is usually more pronounced, “no one has ever done those things with these tools, how do we even begin to do it?” ...

A lot of the rest of the apparent difference comes down to format. The Trek that we remember had to be rushed and crushed. The episodes were short and the TV stations reserved the right to show them out of order, so just like virtually all TV off that time, there was typically a short circular arc by which everyone at the end of the episode must more or less be however they started.

One really interesting thing someone pointed out to me about reality TV was that it was extremely cognitively complex for its time, and indeed this was its selling point. People watched Survivor because something changed as a result of every episode and there was a lot of mental stimulation of the form “ooh I wonder who would be the best strategic target for him to take out?!” . There was a little of this in other places; I like to think about how we used to debate whether a French chef should really challenge Iron Chef French Hiroyuki Sakai, or whether he should have the audacity to fight the nearly undefeatable Iron Chef Japanese Rokusaburo Michiba. But even those shows returned mostly to the same place week after week.
If the book was inspired by/based on an actual trip, then it doesn't need to be mentioned in the book, one can just check what motorcyle was used in the trip, no?
It's a joke about https://en.wikipedia.org/wiki/Edsger_W._Dijkstra
proof is in the pudding on that one, sorry don't think there are academics studying this but it's an obvious outcome from the war that was Go/Scala/Node. Go is eating Scalas lunch because its easy to understand and communities are stronger than individuals. Sure Scala has more 'features' but Rob Pike would say every feature has a cost and you need to weigh that, didn't see that ever happen in Scala. Go is taking the time to get each piece right and I'm glad for it.
The problem with scala is that academic goals sometimes don't align too well with "industry needs".
I guess that's the one:

https://addons.mozilla.org/en-US/firefox/addon/dom-delete/