skysight-inc/HackerNews huggingface dataset:
I don't really see where the humour is here, so just on the off chance you genuinely don't know: Yes, it does.
> Note that this is also entirely possible for engineers.

How exactly? Most people cannot take their code with them and show off. It belongs to previous employers, and please do not begin with the "show me your GitHub" - it's unrealistic to expect people to devote their life 100% to coding. Just as I wouldn't expect a carpenter to build houses for fun in his spare time, I do not expect programmers to spend their spare time in front of computers. In fact I believe that socially it's a benefit if they have other hobbies.
Hacking my spouse phone was really easy with the help of JEAJAMHACKER@GMAIL.COM and now am enjoying what I paid for. Thanks to JEAJAMHACKER@GMAIL.COM MY VERY BEST HACKER.
Yes, it does.
We'll blog about those use cases during the summer.
In practice, the language gives you enough rope if you don't think or care about design at all. This is a typical beginner's problem once they get past their first toy programs and try to write something useful.
As touchscreen interfaces and android auto integration creeps almost in EVERY car market, I can't be not target audience.
"Automation eliminates jobs" comes from people misreading studies on computer manufacturing. One manufacturing employee produces much more computer than they did in 1970 - does this mean the other workers were automated away? No, it means computers got thousands of times cheaper for the same product.

The US employment rate is the highest it's been in 50 years.
Processed photos and videos: Google Photos and YouTube. As an insider I know that I can't afford to match the availability of those and having the live display copy indestructible is soooo convenient. Downside: I don't think YouTube will give you back verbatim input material. Photos will, but it can be expensive.

Raw media material after processing: single local HDD and a remote raid.

Home directory: two local time machine HDDs and a remote raid copy of head.

Unpublished code: home directory + a private git server.

Published code: as unpublished + GitHub (which I assume to be indestructible too).
As you explained, HAProxy does support OCSP stapling through flat file, but also support it through the runtime API.

v1 of the ingress controller does not update OCSP. That said, this is planed for a next release.

Stay tuned :)
We made a bot for slack which provides voice summary for web pages, it is invoked by @larynxBot [URL] to get the audio summary of web content right inside slack[1].

I didn't specifically target this as utility for visually impaired users(as we weren't able to test with such users), but was under opinion that it would help them if someone from the team shared links with our bot.

Reading your comment & that of others reg accessbility on slack makes me wonder if even when audio summary of URLs is received, whether someone with accessbility issues can click the player button.

[1]:https://larynx.io/#larynxBot
Show HN: JExcel – Create JavaScript web based spreadsheets – MIT License
Totally agree: touch screens represent a compromise on usability when it's needed for flexibility, but are almost universally worse than a purpose-built tactile control.

Perfect example: I have a pair of noise-cancelling headphones which let you change volume and switch tracks by swiping on a touch-sensitive earpiece. It's mind-boggling to me that this was chosen over knobs and buttons: first of all it's really easy to accidentally trigger the controls when adjusting the headset. Also, since it's situated in such a way that you can't see it while you're operating it, it's exactly the type of interface which would benefit most from tactile feedback.
I have never used SOAP/WSDL. What was particularly good or bad about them?

Only heard coworkers rant about the XML stuff...
As a dutchman i beg to differ.
How an Optimizing Compiler Works [video]
The natural world will end for us when it can no longer sustain us. All these exploitations may be technically feasible according to a certain worldview, but we will not be there to carry them out if our belief in that worldview leads us to extinction.
Of course bad fathers are mentioned. Bad male behavior is called out all the time usually with adjectives such as toxic, aggressive or predatory. And in many cases the default is to assume a man is bad and then wait to see if it's otherwise. I'm pretty sure it as default policy on one UK airline to never have an unaccompanied minor next to a male passenger.
Big fan of sparkjava for no-nonsense HTTP services. The days of tomcat-for-everything were not fun as someone who only occasionally dabbled in java back then.

So I have to build this as a special type of jar and then set up this other, rather opaque, set of stuff and deal with all sorts of nonsense ...

Now?

get("/hello", (a,b) -> "Hello World");

And we're done...
Whirlpool told to recall dryers in 'unprecedented' government move
10M Storage I/O per Second from One Thread
Indeed, IIRC the intention was to define the meter so that the distance between the North Pole and the equator at the meridian through Paris would be exactly 10000 km, making the full circumference along that meridian and the one opposite it 40000 km.

EDIT: that information is already in the article, making my comment redundant and unnecessary.
I see a lot of claims about "forced tech transfers" to Chinese companies.

This is a completely ridiculous complaint because none of those transfers were forced. All of them were approved by American, European, Japanese and so on CEOs, not because anyone forced them but because they desired to gain themselves a lot of money, maybe also because their companies gained a lot of money in the short term, even if the deal was bad in the long term for their companies or for their countries.

Why do you see anything wrong in the fact that the Chinese were smart enough to negotiate good deals with their Western partners ?

You should blame the American etc. CEOs, because they were stupid and greedy, not the Chinese.

I had a former colleague that more than 10 years ago was detached by his company for several months at Huawei, teaching them how to manufacture mobile phones.

Already at the time I believed that it was a stupid technology transfer, and obviously, after a few years that Western company had to exit the mobile phone market, because, unlike Huawei, it was no longer competitive.

But again, none of those technology transfers was forced in any way.

I have no doubt that the Chinese conpanies, like many companies from USA or other countries, have also stolen some IP, when there was any opportunity. Nevertheless, having experience in mobile phone design, I am certain that whatever they have stolen was much less than what they have just bought from willing partners.

Moreover, it is obvious that during the last years they have improved a lot above whatever they have bought or stolen and now it is they who should fear that the Americans might want to steal their IP.

Supposing that the claims about IP theft are true, then the Americans should have presented some proof and they should have applied sanctions many years ago, because if there was any IP theft there was much more of it 10 years ago then now.

As it is now the USA sanctions look like commercial fraud, i.e. you have US companies that first lure you to buy products from them, claiming that they are better than alternatives, so you invest a lot of money in developing products that include US components, then, from one day to the other those US companies refuse to sell you their components causing you huge damages, as you might need a year or more to redesign everything to avoid US components.

This is a lesson for any electronics designer from any other country except USA, that from now on in any new project they should avoid components made in USA like the plague.
Maybe, the point is not to make it easy. Maybe the point is to make you think "Hey, there's no safe way for me to navigate through 10 different screens to get to my GPS while I'm driving. Maybe I should pull over and do that instead?"
Whatever happened to all the companies working on providing tactile feedback on touchscreens many years ago?
Good, IMHO if using phones while driving is dangerous, then it makes zero sense to use touchscreens all over the place in cars. However some features could still benefit from it, like navigation and settings screens - all those things that can't be handled by a single button or rotary selector, so you'd still have to look down at it to use it.
>it was soft-real time: the delays were predictable and you could learn them too.

Wow, well put! This is definitely something that we lost with the current gen of interfaces, and this articulation didn't occur to me.

Losing keypresses or clicks/touches at random, unpredictable freezes and/or delays on interactions, all this contributes to a general sense of unreliability and not being able to infer the state of the device. Consistency is actually a much more important metric than just plain latency.
99% of the time I see DI used in Java it is solely to enable mocked dependencies in unit testing rather than injecting different production implementations depending on environmental differences or something like that.

I have had Code Reviews where "This is all good, but you should use Guice to mock X" where X is the one time I might have a package-private test only constructor with a NullObject for the one dependency I need to mock out in a commit and Guice is not currently used in the package at all.

Personally I think DI has reached cargo cult status in Javaland.
if it was so, drug dealers would retire after eliminating their families poverty. (Granted, retiring from that line of biz has its complications but it can be done)
Just accusing consultants it too simple. This mindset is prevalent in whole software culture. Think leftpad.
If that's what it takes, then so be it. The yearly road toll is embarassing. It wouldn't bother me one bit if all device input turned off as soon as the car started moving. Passengers can play Eye Spy to pass the time.
I write quite a lot of Java, and I have to admit I never “got” Spring.

I’d much rather have explicit boilerplate code (preferably in library form as much as possible) than complex, invisible magic.

The latter is “easy”, but the former is “simple”. In most cases, “simple” is more important.
In my experience hiring, the diligence to sit down and practice code tests correlates very highly with being a good employee. Just like strong academic achievement at good schools.

That's not to say there aren't gems in the rough who don't interview well, or skipped college, or who didn't go to good schools. But there's a huge time cost to looking for them.
> Chopin, Liszt, and Beethoven were absolutely writing to put bread on the table, and absolutely did not play to the score as written.

Is whether or not you play the score as written an issue? How do we even know this about composers that predate recording technology?

I'm not wondering if maybe the advent of recording technology might be the source of the modern distinction between classical, pop and jazz.

Something that struck me from the bit you quoted from the article:

> > In general, a classical composer uses music to express his deepest emotions and experiences.

I think that might actually be more true of some forms of jazz and pop. Much classical music is very much an intellectual exercise, whereas blues and rock tend to be far more emotional. But again this varies wildly within each genre. Hardly a meaningful distinction.

There's a massive difference between pre-20th century classical music, which was very much the pop music of its day, and modern classical music, which is often far less accessible and more elitist. (Though there are still many beautiful and accessible modern classical pieces. Interestingly, many draw inspiration from jazz.)
For junior positions, I tend to ask very simple questions. Reverse a string or given an array and an int count how many times that number occurs (or variants thereof). Something that requires a loop and some ifs. It opens the posibility of endless discussions about extensions, refactoring, runtime, edgecases - it gives a solid bases on which to judge their ability.

For senior positions, it's slightly more advanced. But if they make it through to second round, we have them bug hunt and refactor some piece of code.

Programming is a craft and I need to evaluate that craft.
I'm not sure they are comparable.
One force of VLC is that it litteraly runs everywhere.

MPC-HC only works on windows, so it's not comparable. mpv has also a lot of target platforms, but not as much as VLC. It's really nice though, and I think a bit of competition is good.
This is not the only reason.

Who started using Java way before Java 8, used to experience serious issues about memory usage and performances in the JVM.

These memories struggle to leave.
This website is one of the accessiblest things (for screen readers) out there. I have never seen alt text for layout images. This is well beyond amazing.
> I pity those forced to work with old techniques

java modules broke a lot of software that were using sun classes or did classloading magic.

I was on one of such application, it's not a lot of effort to migrate forward, but many of the issues are runtime only so unless you have a good test suite, a strong incentive and no closed source library that use some such classes you can't really move forward with it.

anyway, in java 7 was already possible to write "unbloated" code, especially with the servlet 3.0+ spec, but spring and osgi have a lot of inertia in the enterprise community, meaning most people were stuck programming in xml, one of the most unpleasant experience ever.
What Is Natural Language Processing and How Does It Benefit a Business?
Yeah, my daily driver was an Audi with a rotary dial for about a year (no touchscreen at all), and Android Auto was great on it. You get to know the structure of all menus and can take actions blindly after a while. It's been almost a year since I've driven that car and I still know exactly what to press to show alternative routes in Google Maps, for example.

Later I had a bunch of rentals with touchscreen Android Auto, and it was less convenient and less safe than rotary dial Android Auto.

I wish Audi would've kept the rotary dial when they added a touchscreen in their latest infotainment revision.
Here is a great video on TempleOS and Terry Davis himself.
It talks about the development of the OS, it's history and his life in a chronological order.

https://www.youtube.com/watch?v=UCgoxQCf5Jg
I find it fascinating to hear tech people hate on touch screens, when this is the best-in-class feature about Tesla. Can HN be consistent?

The reality is that people prefer more features than less, and buttons are not the best way.

What you probably hate are old, unresponsive automotive touch screens.

The future will use more microphones, be faster, use AI to predict what you want to do, etc....

But this seems like a "pop opinion", popular on the internet, but little basis in reality.
Apparently the instrument is more like one of Hans Haiden's Geigenwerke than Leonardo's viola organista concept, though the two are similar. https://slippedisc.com/2013/11/leonardos-instrument-no-its-a... WP: https://en.wikipedia.org/wiki/Viola_organista . See also the hurdy-gurdy (of course), the Wheelharp https://www.youtube.com/watch?v=VP2iMdvMN5U and the Gizmotron https://www.gizmotron.com/ .
ThinkGeek closes website, moves in with GameStop
Thanks for the tip! But it doesn't seem to present the floppy data as a file system :-(
> Most people cannot take their code with them and show off.

And if someone turned up with code from their previous employer, that'd surely be a huge red flag anyway.
Yes, and the algorithmic tests are highly biased towards those who've focused on that (either through academics or by self training afterwards) - and a miss on these questions still doesn't tell which is the correct story. Then again, this might not matter. Firstly, everybody knows these types of questions are to be expected so everybody cab prepare. Secondly, the problem (from an employers perspective) might not be the false negatives, but the false positives.

This in turn points to that we might try to generalize this a little bit too much, with assuming there're generally applicable ways for software developers but rather we need to adjust the process depending on the type of software development context. If you're developing a web service of minor scale, then algorithmic questions might be stupid (because the knowledge needed is rather one of network, async, web and structure rather than solving math problems), but they might be relevant for Google (where they are might be relevant because they search for developers with that mindset and who can use that mindset to come up with and solve big problems in a certain way - I don't know because I lack insight into the developer strategy at Google).

As engineers and developers my experience is we tend to love to generalize, even when it's not wise to do so.
Mine also. ¯\_(ツ)_/¯
The end of the book 'The PayPal Wars' gives fascinating context on how development just completely dies in a corporate environment. They went from being able to roll major new features in a weekend to requiring months just to schedule a meeting to discuss a font change. It's a fascinating read when we now look back at how PayPal just stagnated under Ebay's ownership.
It's a benefit to the business. There are way more variables of interest to consumers in a car than just UI; few if any will take a crappy touch UI as a dealbreaker (especially if everyone does crappy touch UIs). So it's a pure win for business - the downsides never reach them, they only materialize on the user end, large enough to frustrate people and maybe even cause accidents, but small enough to not cause a purchasing decision change the next time one is in a market for a car.

(I need a term for those cases. Psychological externality?)
Iterate a few times and expectation and mean start to matter
That sure looks nice, but how often do you write services which return a single constant string? I like to judge languages/frameworks based on more representative snippets.
It is contact[at]exodusorbitals.com, unless you already found it!
As a fan of Java I absolutely agree. Having worked with python and C codebases as well, I think every language has its own particular "degraded mess" version. A sublanguage of hacks built up over years of deadlines, inconsistent bugfixes and evolving paradigms.

One nice thing about Java (compared to C and python at least) is that you have quite a bit more tools to refactor and despegettify codebases incrementally.
But with Go you can iterate quickly compared to java as the compilation time is very small. This difference is massive in big projects. This is an important reason why I took up Go for many projects.
But you don't need to interact with the car without looking, that's only for those driving, so tactile interfaces don't give much/any gain.
Glacier is wonderful. I am able to store basically everything I want and it costs me less than $1/mo
He thing about soap was that it was not simple. You had a full object model which was separate from your language and used different semantics. Operating it require a library which wasn’t often nice to work with. It’s the same argument against ORMs. If the library is bad, the ORM becomes a worst common demonominator interface.
I might post it again in the context of OPS_SAT workshop results.
David Novick's Color Illusion Page
And if you don't reply within 24 hour: fired. By me at least. (don't be silly, I don't have the power to fire anyone anymore).

Yes, expecting a reply by email sooner than e.g. 4 working hours is futile.

But if you work in a team and only communicate once a day then you are not a team member, you are an ar#eh#le.

If you constantly check your emails and slack and write replies immediately then yes, we should probably have a chat about your time focus and productivity. But checking your emails quickly once an hour is common sense. And where appropriate with a quick receipt response, not a full answer.

And e.g. slack every 15 minutes or half an hour. Perhaps in a Pomodoro break or similar. (channel dependent)

It would perhaps be a good idea to have a well-known team/department convention on response times. More asynchronous for email especially if not internal (hours not days). Quite asynchronous in company-wide public slack chats, and more responsive but not instant in team irc-like chats.

Whether you program, write content, make sandwiches etc is no excuse to be an ar#eh#ole.
I find the Java love/hate intriguing, I personally like the ideal of 'getting the job done'.

Pre Java 8 is just fine, I don't think it's materially changed, I think what has changed is perception i.e. the realization that all that Enterprisy cruft 'does not equal' Java - nor do wee need FactoryFactor patterns.

My wishlist:
- Stream syntax was nice, but a little clumsy
- In addition to data objects, some kind of 'un-typed' object (better than a Map) for dealing with json-ish type data, right in the syntax.
- First class functions instead of lambdas
- Async notation as a better way to express threads, or even combining within the same thread
- Union types

For compilation, you should check out Graalvm, which has some neat new features there.
I found ae; later versions build but they're kinda big (45kB, yikes), and while the unobfuscated early version is amazingly simple it handles redraw by refreshing the entire screen on each keypress. If you've got curses that's easy, and quick, but if you don't have curses, hrm. CP/M terminal emulators are frequently painfully slow and you want to minimise screen refreshes.

Right now I'm wondering about writing my own in another livecoding session; that original ae is a masterpiece of simplicity. The trickiest part would be handling screen updates... https://groups.google.com/forum/#!topic/comp.editors/335qpDF...

Re Amstrad emulators: I haven't played much with these, but I'd probably suggest Joyce: https://www.seasip.info/Unix/Joyce/ That said, I've been running the Kaypro cpmish port using MESS, and it's surprisingly solid. There's even a good debugger. So it might be worth giving that a try.

Re microcontrollers: there are very, very few Von Neumann architecture microcontrollers, and they're mostly just boring low-end ARMs. The one exception is the MSP430, which is nice but still not a Z80. I think the eZ80 is all there is.
Which carrier? Maybe this has changed but it was not the case when I was living there 7 years ago.
Yes @ absurd level of abstraction, EnterpriseFizzBuzz even manages to laugh at this old-school 'Enterprise' style of writing code[1].

Some enterprises have managed to move away from this though -- DevOps in the enterprise is real and it looks pretty similar to DevOps elsewhere.

I've worked with teams in very conservative enterprises that have automated tests and CD pipelines, and release 100s of times a day, and support their own code. And with their newfound autonomy -- no more diktats about "use J2EE" from up top -- these developers did what smart developers do: simplify and reduce dependencies and tech debt. Lots of vanilla JS (or maybe React at most), plain old Java, even Kotlin and Clojure where possible (microservices made polyglot development really easy).

I've always thought this was a big reason Oracle dropped J2EE. Their most conservative customers weren't interested as J2EE had become irrelevant for their needs.

Here's a public video of how one institution (JP Morgan) managed to modernize[2].

[1] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

[2] https://www.youtube.com/watch?v=Tyev4Ti9Xsc
Let me guess. Motorcycle rider? (_Fellow_ motorcycle rider...)