skysight-inc/HackerNews huggingface dataset:
Some of these grievances might be better titled "things that thew me off when learning React".

I'm not quite sure how using "className" vs "class" materially affects a complex project.

propTypes are pretty shallow in terms of checking, but I've seen them more as something third party components should provide as metadata/documentation rather than replacing a type system. Large project should rely on Flow or TypeScript if they're worried about typings.

I'm not sure I follow the complaints against asychronicity? Maybe when dealing with improperly complex components it becomes tricky and that I think takes experience to get a feel for.

Additionally, if we're comparing what appears to me to be a synchronous two way binding pattern to React, I think it's really just a matter of choosing the wrong technology for a given preference. React and the omnidirectional data flow pattern are directly opposed to that.
Not really: GMO crops don't really use more pesticides. Very often less.

It's not totally a one-way street and things are complicated in many situations, but the common public perception "GMO == pouring lots of pesticides" is clearly wrong.
The message boards on IMDB is nearly the only reason I ever go on IMDB, just after watching a movie. I never go there for their content since there are much better sites out there presenting the info (themoviedb), + there trailers are terrible slow to load (at least where I live) compared to Youtube or even Apple hosted trailers.
I'm not sure what your exact requirements were, but I immediately thought of the following:

* Beamer: write slides in LaTeX, maintainable for a long time to come and easy to build.

* Reveal.js: use JS and HTML to author slides, easy to present, and pretty maintainable I think.

* Pandoc[1]: use Markdown or RST to write your slides, then compile to HTML (e.g., Reveal.js) or LaTeX (Beamer).

* Google Slides

I'm not sure if any of these (except Beamer) were available back when you wrote the tool, but given some of the complaints in this thread (e.g., not mobile-friendly), wouldn't it make sense to migrate to some other tool going forward?

[1]: Absolutely fantastic tool all-round, and written in Haskell to top it off. I used it a few years back to write a LaTeX report in Markdown. It's definitely not as good as writing LaTeX directly, but it's a great place to start. I can't praise Pandoc enough.
I don't think it has the 2nd pair of legs/arms just for balance!
The fact that the air jet can target individual bad peas out of that torrent is incredible. Computationally, probably not that difficult, but the timing required must be ridiculous.
i think a couple of years of experience and learning a new language .. was a far bigger factor than any intrinsict characteristics of go
Once you know whatever java framework well enough and your project is not something ruby on rail spits out immediately, shipping fast is not a problem. In 4 months timeframe, you can definitely produce more or as much as with node.js or something like that.

The issue is that you wont do good frontend in it (obviously), java programmers are more expensive, learning it well enough so that you can actually be that fast takes a lot of time and hosting is way more expensive. Learning language itself is easy, but absorbing necessary frameworks takes time. Moreover, people who are good in frontend prefer languages similar to javascript, because they already know it very well so those are easier to learn for them.

I think this is why it does good in enterprise - they have money to throw at hardware, most projects are under huge time pressure constantly and requirements change constantly. Frontend is super important for product, but not so much for enterprise.
>It was very very common for female writers to publish under a male pen name at this time because that was what it took to sell.

In these enlightened modern times it is now often sufficient for her merely to use her initials, to obscure her shameful female nature. A famous example: J. K. Rowling.
I've seen people get upset about overreach when the US asked to have a plane diverted / tried to strongarm extraditions / etc. I'd bet a large sum that this story was reported as "...detained while attempting to enter US..." and that nobody batted an eye upon reading it. That is the manufactured consent I was referring to.
Year of languages – ruby
Today's Super Bowl halftime show will undoubtedly be a provocative spectacle
by length: https://www.youtube.com/watch?v=nlCSlJuD65A
I would counter sue the shit outta you.
Making concrete doesn't take that much energy. It's around 130 kWh/tonne[1]. That isn't really all that much: compare to the 280-350kWh it takes to produce a single barrel of crude from the Alberta tar sands[2]. And that energy is increasingly coming from renewable sources, like wind and solar.

That said, Asphalt is probably one of the better uses for crude oil. Sticking it semi-permanently to the ground has got to be better than burning it and releasing all it's carbon into the atmosphere.

[1] http://www.sustainableconcrete.org.uk/energy_efficiency.aspx
[2] https://en.wikipedia.org/wiki/Oil_sands#Input_energy
Could you explain how platform exclusivity is a dark pattern?

When I think of dark patterns I think of misleading ways to get a customers information where not applicable. I don't see how it's a dark pattern if I can't watch Game of Thrones on Showtime or Orange is the New Black on Hulu.

Why is retaining rights over content creation a bad thing? Is it a dark pattern to have companies pay for licenses or copyright fees?
HL7 has matured even more now.
The linear evolution from HL7 v2 to HL7 v3 did not win the day. Most are now moving to https://www.hl7.org/fhir/

Main issue is with HL7 is not technical. From a business point of view, the incentive to cooperate with other systems via HL7 means another reason for a department to adopt a system other than yours.
Ask HN: What should I know before requesting a freelancer to build a site?
I've used freelance websites like upwork before but the quality was shoddy. I typically write up a "scoping document" where I describe in detail every feature that I want my site to have + what the site's user is expected to be able to do. However, I have very little experience in web design - or what would make my site look good - so invariably, the finished product looks amateurish due to (a) poor experience from my side and (b) the freelancer not caring or willing enough to come up with a good design. I guess it's because I've gone with web developers in the past and not designers?

Note: I'm not worried about cost - i.e. I am willing to pay a lot for good work.

So say I've a good idea now, and would like someone to build the website for me.

How do I go about getting the best out of freelancers? Should I put up separate requests for the project itself, and have another freelancer design the site separately?

Would really appreciate any type of advice.
Oh there's some overlap as in all things very little is binary.

None the less PKD doesn't really tell "human vs technology" stories. Take for example "A scanner darkly" which is an interesting psychological thriller and story about chemical addiction. To quote the wikipedia: "A Scanner Darkly is a fictionalized account of real events, based on Dick's experiences in the 1970s drug culture. Dick said in an interview, "Everything in A Scanner Darkly I actually saw.""

"Man in the High Castle" is alt history action. Its not really a story about technology.

"Blade Runner" is film noir action flick with a dose of moralizing about racism and dystopia.

I'd say the thing that defines PKD is technology as escapism. Yeah OK "a scanner darkly" is about speed freaks but he wanted to tell a psychological thriller about addiction without people casually tossing it away as "the speed freaks movie" so he invented a whole substance D mythology to prevent people from taking the easy way out in their analysis. Ditto Blade Runner where the technology was a cloak to hide aspects of modernity he didn't want to talk about, not a central part of the story.

Sort of like how some fantasy pencil whips away aspects of the modern world the author doesn't like in order to pare down to just what the author wants us to focus on.

Technology as a zoom lens, not in the zoom lens. PKD is a cool author but in many ways he doesn't even write sci fi.

How about another definition, soft sci fi can be turned into any other scenery with mere cut and paste, and tada "a scanner darkly" is about elves smoking too much pipe-weed in Tolkien world. But hard sci fi requires a major and substantial rewrite to change the scenery, not just cut and paste. KSR's Mars trilogy isn't going to Venus or ancient South America any time soon.

The problem with the carpenter you mention is out of millions of pro and maybe a billion amateur/ancient carpenters only that one had much insight. Its a bad odds game.
> note: I expect serious down votes as opposing Babel is almost a serious crime nowadays and proves my unlimited stupidity.

This breaks the HN guidelines (https://news.ycombinator.com/newsguidelines.html). Please don't.
Hmm, interesting. For many people, it looks like their open office has people taking phone calls at their desk. We take phone calls in rooms (which you book on Google Calendar). If there are no rooms available when you book you reschedule or take the call in the Team Room (which has no expectation of noise-level).

If people are loud, you talk to them about it. It almost never happens since your coworkers are respectful and since you've obviously kept the more noisy jobs in a different part of the office from the engineers.

It seems to me that single person offices will suffer heavily from Conway's law.

But we'll see. It looks to me like where I've just moved to has no call rooms and no separation between engineering and the rest, so I'll see if those factors alone will change me from pro-open-office to anti-open-office.
This one is pretty impressive. :-)
https://www.youtube.com/watch?v=m7Gs6-6p7qw
Ide makes learning easier and faster instead of harder. You dont have to care about compiler passes, ide compiles seamlessly.

But yeah, learning java ecosystem well enough takes a lot of time for someone who is just starting and you have to be comfortable with abstract thinking.
I work for a company that specializes in incorporation and compliance services. We have a free information center that contains a lot of information and guides that people may find helpful: https://www.harborcompliance.com/information
Most of my work is C++ but I've also used Go a fair bit since Go 1.5. I like Go a lot. The C++ crowd (including myself) keeps trying to make things that are trivial in Go easier in C++ but the best efforts still look like a mess. I think the lightweight/green threads model of concurrency wins over others (threads, processes) and is incredibly difficult to get right in C++. Channels are also very useful and difficult to get right in C++. While C++ with some aid from Boost can be a very safe language it ends up being a lot harder to write and read with all sorts of [](){} -> hacked up conventions that are a result of backwards compatibility. I find the test infrastructure in Go to also be very pleasant and easy to use. Stuff you need to go to extremes of C++ to test are just trivial to do in Go.

Things I would like to see improved:

- Package management. I think "go get" was an interesting idea that is basically a fail for anything except the most trivial of situations. Vendoring is not a great solution either IMO. Perhaps some idea that manages package versions through local git repositories can work better since a git repository is a better representation of the version history of packages.

- I didn't like the compile speed loss we took when the compiler code base moved to Go. I'm not quite sure where it stand right now but one of the things that I liked about Go from the beginning is lightning quick builds.

- In my usage there seem to a few quirks in the language including the various scoping weirdness and the declare and assign operator := ... I frequently end up with code that re-uses the same variable such that the first instance is := and the next are = which makes refactoring a pain. The compound if statement also suffers from this.

The uppercase/lowercase public/private convention is also odd. You get used to it but it seems like a hacky afterthought.
Still working on the elevator pitch. Unfortunately it's not as obvious as something like "Facebook for cats!" (Although I think it will be much more useful)

The general idea is to be able to have informal, unstructured business conversations, take those conversations and type extremely brief, semi-structured (tagged) notes, and have those notes "compile" out to various places throughout the organization where they might be needed. One way to think of it is Requirements/Use Cases/User Stories without the rigor. (Or rather without the rigor and onerous BS folks constantly seem to be always adding around them)

Here's the repo. There's also a PDF with details of the tagging language I can send if you're interested. Ping me.

https://github.com/DanielBMarkham/easyam
Applied AI will be the next "nobody knew how fundamentally things would change."

I don't believe in the singularity (at least as currently envisioned) but I do believe we need to figure out what a society must look like when most human beings are, almost literally, not useful for commercial employment.

Like, the whole tenets of a market economy and capitalist ownership will smash into the tenets of human worth and the function of society, with violence and consequences much greater than we've seen until now.

We can see it coming. It's obviously clear. And nobody in charge is taking about it, much less doing anything about it. A totally avoidable tragedy, walked into on purpose.
I don't think the author of this article really understands what React is and what it is not. They repeat several times that React is a framework - it is not. React is a library, one which you can use to render components and build interfaces. It doesn't claim to be a Framework for handling data, and making comparisons between the number of lines required to write tiny TODO applications isn't exactly convincing when the argument is that you shouldn't use React for complex projects.

The author writes off solutions such as Redux which are designed to solve nearly all of the "problems" the author assigns to React because they add extra layers to the application, however in reality, separating your data and your views is EXACTLY the point - that's what helps to make complex applications manageable.

The article is really an advertisement for the authors own framework Binding.scala, rather than a critical look at React.
B specific. Answer the question above, name the problem you have on mind and tell us how is brutalism solving that problem.
> why math is so successful in the real world

Well, math is a universal approximator -- if there are patterns in what we observe of reality, math can fit them, but that's a far cry from them "being" math. Other formal systems like Turing machines or Lambda calculus can also approximate anything (including each other, naturally) with different primitives... and they have an easier ontology (as far as I can tell). I mean, if you posit that fundamental reality is a computer of sorts, you get your ontology, and you get math as a very good formalism to describe the particular program we're in.
Voltage isn't particularly relevant of itself; what's that in dB above the noise floor?
"Is there some point where websites start to significantly displace apps?"

It seems to me that this is already slowly happening and this instant app thing is the reaction. After all, Google would lost the control if everybody started to use the browser.
As a bioinformatician, I can tell you: no. Hardly anywhere you have that concurrency need. You have a few clients only, typically, but with very highly parallel work-loads (as opposed to concurrent ones). Go is a bad for there.
Totally agree, but some people get it for the sport. I just go to the pub or local bowling club if there is something I want to see.
I see the value in an old-school workplace where everyone has an office. Cubical variations, no matter how pretty, just always feel a bit wrong unless everyone is working on the same project.
Personally I think the backlash against colleges is just starting. Diversity of opinion should be encouraged, not stomped out because you feel "challenged".

With diversity of opinions comes unsavoury or misguided opinions. Then debate occurs and some people might change their minds, but either way both sides growing in the process. Shaming and other ad hominem attacks are lazy, even the ancient Greeks understood this.

> why should I stand there and smile politely while someone comes to my campus and launches a propaganda campaign and recruiting drive for ideas that challenge my way of life

It's a bit self-centred, no? And also ironic, that campuses are so dominated by left ideologies that different ideas have to come from outside, and then are rejected by the uniform group think on campus.

Safe spaces are disingenuous and counterproductive for preparing students for the real world. After college, nobody will protect you, unless you live at your parents. Especially if you've travelled, you know this. If you don't push the boundaries, you don't grow.
Math won’t solve quantum gravity. Experimentation will
I don't think Ken Thompson meant to omit the names of Paul Karger and Roger Schell. At the time it was often extremely difficult to find a paper unless you already knew where it was. Whereas today you can do a search and instantly find it and read it: "Multics Security Evaluation: Vulnerability Analysis" by Paul A. Karger and Roger R. Schell, June 1974, http://seclab.cs.ucdavis.edu/projects/history/papers/karg74....

I've had trouble finding some of the earlier work on high-security SCM; I do reference what I found. If you find something important I'm missing, send me an email: https://www.dwheeler.com/contactme.html
Having a turnstile is the thing that would confuse a lot of us, and cause us to look at a reasonable way of getting back out without waiting in the queue.
ZModeler 3.0.8.1061 – Download
Visiting D.C.
This isn't always a solution. I've often been tied to 'my' devkits, for example. Or 'my' tower of tablets I'm trying to port to and support. I've gone as far as buying a cheapo extra desk out of my own pocket because I was running out of space in my spacious L shaped cubical, and needed the extra surface area by forming a U. I've also had nontrivial amounts of dead tree documents.

Basically, I often labor under constraints that make it unreasonably expensive and difficult to make workstation hardware interchangeable like that.

My dev environment would be difficult to virtualize as well. I've dealt with pre-release software, pre-release OSes, and any VM based solution would need to give me proper GPU access. I'd need to develop tooling to help manage constantly reconfiguring my tools to point to whatever devkits are local as well. Syncing data is another problem - right now I often abuse symbolic links to move 'cold' projects and tools off of my SSDs, as 2TB SSDs only recently became affordable.
Does this work on mobile?
Sure, many "modern" sites have terrible UX, but that doesn't mean that minimalist or "brutalist" designs are intrinsically any better.
I think now, in some fields, even experts can't predict. Look at what happened with the game of Go, and probably Poker. No expert, except the real few ones who did the actual job, thought that a computer Go could beat a professional human player. At the same time, even with these surprises, we don't know if the singularity is near or very far.
Agreed, riots aren't necessary anymore -- but that's only because you're fast-forwarding by nearly 50 years. The anti-DoMA movement, the bathroom bills and all the other modern wins are but the culmination of a decades-long process. The prevailing opinion on the LGBT community is that they never would have gotten anywhere near to where they are now (or at least never would have without an unacceptably long wait) without Stonewall (or some similarly cathartic moment).

That is, without a moment when those affected came forward to not just demand, but to claim and assert their rights when the situation called for it.
> If you go look at Mexican peasant farms from 50+ years ago

The goal of modern agriculture shouldn't be to produce like peasants.

Their output was low, product homogenous, and crop was prone to catastrophic failure. All very bad things.

>e the fundamental lack of genetic diversity in our modern industrial agriculture system.

Diversity is a renewable resource. Even despite that, there already exists an incredible library of diversity breeders use to create yearly hybrid crops. The reason only a few types are planted each year is because they are optimized for that season.

Stop assuming modern farmers don't know what they are doing, and stop leaning on an authenticity bias of yesteryear.
Cubicles keep the talking down.
Well, there is; it's "regular" OS LTS.

Ubuntu won't change the GUI during LTS (5 years).
You know, I'm past worrying about the feelings of trolls. They're not owed fun or any protection for the activities they enjoy, and if they don't like getting kicked out of civil forums for acting like assholes then too bad.
We ban accounts that comment like this. Please post civilly and substantively, or not at all.

https://news.ycombinator.com/newsguidelines.html

https://news.ycombinator.com/newswelcome.html
I disagree with at least one of the authors critiques:

"Issue 1: React components are difficult to reuse in complex interactive web projects.

Such a lightweight component is very handy in rendering plain and static webpages. Nonetheless, when there are interactions between one component and another, passing callback functions as parameters are inevitable. Particularly for webpages with complicated structures, we have to nest dozens of components from the inside-out, where those callback functions are passed through from parent to child components across layers and layers. The only outcome for applying React framework in complex interactive web projects is that the codebase would become too messy to maintain."

Out of the box React is relatively spartan, which is great for small projects. At scale it only really comes into its own when used in conjunction with other things such as Redux and its wonderful ecosystem of middleware.

In this kind of situation, I would advise using something like Redux and following the advice of Dan Abramov (Redux creator). He wrote a wonderful article on how to split functionality between components and containers:

https://medium.com/@dan_abramov/smart-and-dumb-components-7c...

I think this is a great pattern to follow for larger scale projects.

"It is well-known that React is a great tool for implementing simple interactive websites, but how does it apply on complex interactive front-end projects?"

Facebook seems like a pretty complex website to me and they are all in on React.

As to his points about the virtual DOM performance, I'd love to hear a more experienced web dev chime in on that as my area of expertise is native development.
Wow, thanks very much for sharing that!
Or you just drive a car somewhere, and walk away, which is a well tested delivery mechanism with far more capacity.
Carry Lysol wipes.

Or have the employee keep a container of them at each station (if they don't already, which IME many do).