skysight-inc/HackerNews huggingface dataset:
I don't know about Seoul specifically, just thinking it's really disappointing if organizations are building a "Metaverse Presence" instead of using money to have actual people - though whatever medium - help their clients. Would you rather have a metaverse chatbot that can't help you, or an extra person at the service centre that can actually address your problems.

Orgs love to rush to anything that has the promise of not having to employ a real person to help. I wish they'd just give up and spend the money on actual counter or call center staff.
Wow. I've talked with people who "lived outside" and realized that they were in very different situations.

This article does a good job of breaking it down with a simple analysis. It makes me think of the book that inspired this musical

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

which described quite a few different situations people were in.
Here at Big Electrical Equipment Manufacturer we are currently dealing with a cable shortage.
3 years ago, if I would have told the people working here that someday we would have a cable shortage, I would have been laughed out of the room.
1000 kilometer in a 100km/h average German ICE (average on the trip I took including stops in between) is ten hours. Plane flying 900 can do it in one and a half. Even if it's the ideal center center trip and allowing for two hours of boarding and an hour to and from the airport, flying is nearly twice as fast. Now if it were to be the much faster French Thalys they can average 150 (including stops) on the route I did but it's still an hour difference. I'd say French Thalys is competitive up to 700km for direct center center trips. German style HSR is interesting only as an alternative to a car.
Great article, but I didn't see (maybe I missed it) a notice of the fact that homelessness can be correlated with meth, mental illness, etc. with the causation working in either direction. Homelessness could be caused by, or increase the chances of, any of those other factors (or both).
The problem with equality and dynamic typing is rather deep and intractable. Kent Pitman (of Lisp fame) has an entire essay about it: https://www.nhplace.com/kent/PS/EQUAL.html

> If COPY can't be done properly, then neither can EQUAL. And, in fact, that's the case. There is no uniquely determined equality function for complex structures--there are only arbitrary ones.

What Steele says about equality is true for Scheme. Everyone has seen the famous "Wat" video of adding "{} + {}" in Ruby or JS. But no one ever mentions Scheme or Lisp:

scheme@(guile-user)> (eq? "test" "test")
$1 = #t
scheme@(guile-user)> (eqv? "test" "test")
$2 = #t
scheme@(guile-user)> (define x "test")
scheme@(guile-user)> (define y "test")
scheme@(guile-user)> (eq? x y)
$3 = #f
scheme@(guile-user)> (eqv? x y)
$4 = #f

Of course, if you read the RxRS specs then it's all documented and to be expected. But the same is true for JavaScript. As much as I hate typing the "===", there is precedence.

> breaks an important mathematical property

Even mathematicians get lazy and create new syntax and short cuts to express their ideas. Programming is ultimately a human UI. It's easy to see why automatic type coercion was once popular (and probably will be again, I can almost guarantee this).
Most of the time, that's what I expect. However, sometimes when proceeding step-by-step through a large refactor or a large feature addition, the codebase may be left temporarily in an incomplete state.

My preference under such circumstances is to favor clarity of commit history, and leave the step-by-step commits intact — with the requirement that they always be located in a feature branch behind a merge commit.
It's pretty similar in scope. Native GUI on Windows and therefore limited to it.
From the information that they've published (paywalled article excluded of course) it does not seem like they're going for anything necessarily novel or niche-filling, more just making another option. That's not necessarily a bad thing, as (coming from someone who works in BCI) more tech is always welcome, even if it's in what I and most other people I talk to consider a dead-end technology (EEG).

Also funny you bring up the Muse, as I actually worked there a few years back. The Muse 2 is a reasonable increase in signal fidelity though with a tradeoff in that it has more issues in adverse environmental conditions (sweat etc). The main difference between the generations is in usability on the consumer end, which is the target market for the device. It was never intended to be a research tool, and it excludes many of the important electrode locations for research. For that reason, calling it a toy is roughly accurate in my opinion.
Sure. The gist is that Disqus collects your data like no one's business, and other shady things like ads. It's a very popular commenting system because it's free to use and easy to setup, but there's an obvious downside. I would go more in depth but honestly the articles below do a much better job.

https://supunkavinda.blog/disqus

https://jacquesmattheij.com/disqus-bait-and-switch-now-with-...

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
>What other product is regularly portrayed in advertisements being used in such criminally reckless ways

I would say that this is common in advertising for movies and video games. Both regularly depict fantasy behavior that would be illegal if anyone did it in real life.
It just means they will be working for a new company created to avoid the sanctions.
So, I bought one and it was great, but then randomly the CO2 sensor seemed to stop working after a few weeks. It stayed at the exact same ppm level without changing for a while. I sent an email to customer support and they shipped me a new one for free, and didn't even require me to send back the old one. Haven't had any issues since. I'm pretty happy with it.
I spent some time working with the Sphinx source code (the main user of rst), and found that reStructuredText is very poorly suited for porting to any other platform because a lot of the "spec" is just whatever the Python implementation is doing. IIRC it's also not context-free, so it's more laborious to write a parser. "Technically superior" it is not. I also think a lot of the syntax is obtuse.

That said, I really dislike that Markdown does not have any affordance for adding custom markup. Because of that, it's poorly suited to technical documentation; there's no official way to say "insert the autogenerated docs for function X here." Every doc system that uses Markdown invents its own special thing.

So, I think there's still space for markup languages that find a balance between prettiness and extensibility. I did my own experiment that let you define custom HTML tags but didn't have a reason to really finish the project.
> And that aside, do you not like going to a restaurant because you knew you could as soon as you earned the money to buy the meal? Maybe it's not the same as eating a fish you caught yourself, but it's still enjoyable isnt it?

The difference is that I don't want to have a sexual intercourse with the resturant's chef :)
Noooooooooooooooooooooooo. I'm not even going to bother trying to remember the xkcd number about 14 competing standards.
Well you seem like an unbiased interpreter of the available data. Good luck.
Even simple stuff takes me multiple tries. I don’t know how any engineer gets a design right the first time. I can build it in a 3D design app, look all around it, and STILL see something in the prototype that was not obvious in the design.
I don't agree that everything has to revolve around MVC. It's not a hammer for every problem. This is why other patterns like MVVM, MVP and other abbreviations were introduced to solve broader needs.

React starting as purely a UI library paved the way for people to find new ways to manage state and data for different kinds of applications and needs. That's how we ended up with what we have today. You can say what you wan't, but I think it's remarkable what people came up with in the past 10 years.

And these solutions are just optional things you can choose in case you have a need for them. React comes with a lot of things for building rich UI. Sure some things may require more code, but so is the nature of writing applications with specific requirements.

Server components, Concurrent Mode and Suspense came out of the frustrations that it was hard to provide great user experience and avoid common pitfalls with async I/O and high performance because they were limited by React. The solutions they came up with, while not perfect (or even ready yet) aims to solve these issues, while avoiding breaking backwards compatibility and that could be further improved upon while also avoiding breaking the API.

With regards to hooks, I agree that it can be annoying to have to manually pass dependencies. But this is unfortunately the nature of JavaScript and React's mission to not break things. The alternative would require massively changing the API. We've seen other attempts at remedying this with projects like CrankJS and SolidJS that takes a clean slate, preserving the concept of React, but taking a more modern approach on these concepts, as they have freedom of designing their own API from scratch.
Lightsail is just one of the 17 different ways to run containers on AWS:

https://www.lastweekinaws.com/blog/the-17-ways-to-run-contai...
I like this new word thaught, I shall start using it in my belligerences.
Let’s be clear: there is no “THE metaverse” yet. If there ever is, Facebook is unlikely to be the owner/primary facilitator of it. The article’s contents kind of say the same thing. The name change is pure hubris.

If there is eventually a metaverse, it will be an open protocol that can be run on any server. It seems unlikely that a real-world analogue of Snow Crash’s “The Street” will ever materialize though, because there is essentially no public computing space, and no plans for any.

I could be wrong: Zuck might mutate into a real-world L. Bob Rife, controlling the infrastructure and using it to stealthily subvert all of humankind to his own wishes through means that slip under most people’s radars.

Wait, hang on…
It's software. Software's contract is the same as a legal contract. And a legal contract mostly says what you can't do.

So anything not directly blocked by the software is allowed.

Ergo, clear specifications, strict yet flexible types and APIs, etc.

Otherwise, it's just bad design.
Do you mean vernacular term JST as in any little plastic PCB connector including all kinds of gray market fake clones or genuine JST components from JST the company?

Its a single supplier. JST is single company in Japan. I'm sure they're busy doing "stuff" and having fun trying to ship things.

Its like trying to buy Nichicon capacitors. There is one company in Japan making Nichicon capacitors. If they're busy, well, they're busy and you wait. There are zillions of "e-waste" reprocessors in China whom will desolder larger electrolytics from old PCBs, peel the plastic shrink, and apply a new shrink with all manner of trademarked names and temperature ratings to random e-waste pulls, including falsely labeled Nichicon. Those are the only two suppliers of Nichicon caps and if they're both busy or sold out you're outta luck.

Now if you're willing to change your BoM or if your safety regulator permits it and your company purchasing dept has a relationship with competitors and no single-sourcing agreement for better prices, you can use fantastic products from Chemi-con or Vishay or tens of serious competitors and hundreds of not-so-serious competitors.

Because you're doing stuff with JST XH I "know" you're doing something with modern RC vehicle batteries. I'm old, we played with RC cars in the 80s using Molex connectors and had the same problem as now, Molex is a single company and if they couldn't ship we didn't get connectors and that was the end of the discussion.

Full size car batteries are not licensed single source technology. Then again a lead post of a given diameter isn't very high tech. AFAIK there are no rechargeable battery pack connectors that are unlicensed at this time. FOSS type projects to issue a standard connector might arise, someday. Could implement 18650 individual cells and holders, those are unlicensed and not trademarked AFAIK but I have not verified that.

BTW JST connectors are extremely complicated not just wire and plastic. The posts are made with a cheap copper alloy, then plated with thick copper and plated again with tin, and the solder tabs are made the same way. I guess the PITA of a stage of pure copper plating is cheaper than paying for pure copper for the entire post. Copper is expen$ive. The plastic is a weird polyamide nylon-alike with some secret sauce flame retardant mix in that supposedly doesn't corrode copper or tin, so the connectors don't burn terribly well. Nylon usually doesn't burn until it melts anyway. Very hand wavy polycarb would melt or be tiresome to deal with at reflow solder temps, nylon is only like fifty degrees tougher but that's tough enough to make it easy to reflow nylon connectors. Or more specifically it'll keep its shape deep into the decimal places after reflow. They used to make polycarb capacitors from like 1960 to 2010 but they gave up, I guess impossible to hot air reflow them I don't know for sure. Polycarb dielectric caps were good higher-temp milspec capacitors...

(edited to note, if you buy genuine JST corporation connectors the above is true. Fake clones from China, who knows maybe made with copper plated aluminum wire and polyethylene?)
I'm confused by your post. You appear to be aware that this caricature of a homeless person that you've invented is wrong, based on:

> The definition of "mentally ill homeless" is surely nuanced and varied,

but in the rest of the post you appear to be discussing this strawman as if it is the primary concern.
> It's read-only, ofc.

Until one drives the electrodes with some voltage.

Then it becomes Transcranial Electrical Stimulation

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5405830/
And note that the domain name of the St. Louis Fed is ".org" rather than ".gov" like official US government agencies like the NIH, FDA, USDA, etc.
I really miss yahoo pipes.

I played with Huginn a bit, but it’s a steeper learning curve.

I feel like the promise of the Internet has really been blocked off my adding in some nice business models. So now companies don’t want interoperability and orchestration as that stuff just reduces revenue. Why would goog/face/etc want us spending less time doing mundane tasks. They want us spending the max amount of manual stuff as long as we don’t quit.
Because nobody values IT until it's a problem
> literally just javascript

Repeating it over and over again does not make it true.

https://linkedlist.ch/jsx_is_not_just_javascript_39/
I would say no, absolutely not. You should build optional facilities and if people don’t go maybe it’s because your facility sucks. For example lots of places require you to be in at a certain time every night and vacate early in the morning. This may seem fine but it leads to problems for anyone who wants to work a night job or socialize with friends after a day shift.

It seems that housing-first is the way to go. Give someone keys to their own place they can come and go from any time. Offer medical and mental health services nearby. This gives people the time and space to get well and stabilize their life. Using cops to throw someone in to a facility is just one more difficult and disruptive challenge that makes people’s lives worse, not better.
And instead of trying to understand the reason that video had so many dislikes they decided the users and the dislike button are the problem, not anything related to the way they're running Youtube. And that reaction just reinforces the beliefs of people that dislike how Youtube is being run.
Since OCR is hit or miss, I can't see many users signing up without trial/preview of how well the OCR works on your handwriting.

Also would suggest being able to e-mail a photo and having the service reply with a temporary URL of how the site would look.
> On other hand, I've seen very expensive STM32s being used in near semi-disposable goods.

Like a single-use disposable electronic COVID test: https://www.youtube.com/watch?v=UvArprBmdFA (though this one uses an nRF52)
There's tons of crap like that.

Just now found there's yet another public transportation-related money sink in Berlin currently: https://www.schwarzbuch.de/aufgedeckt/steuergeldverschwendun...

It's a frustrating affair quite frankly and bad for my heart.
And some people like a car with a manual transmission but in either case it has nothing to do with KISS when talking about an automatic car. KISS is about removing unnecessary complexity from a design not removing functionality from the design to simplify it.
Not a bad thing, but you should understand the economic ramifications of it.

"No code" is basically commodification. For some subset of IT tasks, there are now tools you can use to achieve your goals without employing a software engineer. Great - it makes everybody more productive when humans can be replaced by software.

But note that commodity markets, by definition, are low-profit. If you can use some cheap off-the-shelf tool to achieve a goal, so can all your competitors. So people thinking they're going to build the next great billion-dollar web startup off of Wix or Shopify are probably going to be disappointed. They can build a great web startup, but so can everybody else. You can no longer make life-changing sums of money just by being able to throw together a website.

It's more useful to businesses whose competitive advantage is elsewhere. If you make complicated hardware, for example, and just want to be able to sell it without paying the Amazon tax, these tools are great.
This made my day! Nothing technical to say sorry!
> So naturally many faculty push off as much of the teaching, preparing materials, grading, handling of office hours, labs, handling student questions, etc on others.

I would count adjuncts and lecturers as non-tenured faculty rather than administrative staff.
> It begins with by questioning "why did Rousseau wrote about inequality if 100 years before no one in western culture cared about it"? Then he goes to show how the themes of liberty and social equality came from Canadian First Nations criticism of western culture

Well, La Boétie's "Discourse on Voluntary Servitude" dates back to 200 years before Rousseau, and I wouldn't say it was inspired by American Indians. I am not saying that the discovery and then the deep relations that France did have with American Indians did not play an important in the literature and reflections: on the contrary just a bit after La Boétie's time, Montaigne integrated them in his thinking. That was still over 150 years before Rousseau.

Edit: There were other major transformations at work, like the fact that before 1500, writers would either be lords or strongly depend on King or lords both for their income and for being allowed to publish. It was a Middle Age organisation, with a chivalry based nobility; writing essays was not a thing, the number of themes was as reduced as the number of forms. Then society organisation changed, bourgeoisie and nobles started mixing more and more; writing was more long-form (technical reasons come into play too) and of course expanded the number of themes it dealt with.
This product isn't super new, blog post is dated Nov 13, 2020.
Query AWS API with SQL
I read that as "set your CI to run earlier in your workday so you don't get new error reports at the end of the day." Midnight UTC being 4 pm/16:00 PST.
> it varies a lot by time of day etc.

That _may_ explain the difference. The officially reported percentage is per train, not per passenger. Passenger onboarding can cause delays (for example, a rural station may, some days, have a school class enter a train. If you make room for that in the schedule, customers will ask why you stop for 5 minutes. If you don’t, the train will be late at its next stop, if that’s only a few kilometers away), so chances are trains with fewer passengers are more punctual. If so, the per passenger percentage of on time trains will be lower.

It also is measured only at final destinations. That percentage almost certainly is higher than that measured at each stop (a train that’s late half-way through can try to make up for lost time, but it can’t make up for being late at stops it already had)

Finally, there the question how cancelled trains are measured. Possibly, they aren’t counted as late, but do delay passengers.
> As a best practice, there's a reason that Linus started git in a separate repo, rather than as part of the Linux project. The reason is that if you put too many projects into one git repo, and it gets too large, you do eventually hit a scale where it becomes a problem.

Nope. The reason they are in a different repositories is that they are completely different things, with virtually zero code shared between them. There is no point in putting them in a single repository. The teams are different, the process is different, the release cycle is different.

The reason people like me use monorepos is not because we mistakenly believe "each company needs only one repo". It's because there is a tangible and measurable advantage in grouping some things together. That's it.

> If you're going to use git, you're going to have the most success using it as intended, which is some logical separation of "one repo per project" where "project" doesn't grow too out of hand.

No, that's patently false and absurd. I had the experience of using one repo per project and it was a horrible experience full of bureaucracy, and I know other people with the same experience. A git monorepo is working fine for my company and has been for years. I know other companies who also feel the same, and no, the "sky is not falling" as you seem to believe.

Claiming that "there can be only valid method, and it's mine" is bullshit. Engineering is not about silver bullets.

> Tragically, I think if Google did opensource their internal vcs and monorepo tooling, they would immediately displace git as the dominant vcs and we would regress back to trunk-based development.

You keep forgetting that not every company operates at the Google level. Git is more than fine for 90% of the cases out there. There is more to tech than FAANG.

> If you ever do hit a git limit where it's no longer comfortable to keep the whole repo on each developer machine, I would encourage you to split up the repo into separate project-based repos rather than switching to Microsoft's git fork.

Sorry to be blunt, but I'm not taking advice from an internet stranger with opinions grounded purely on dogma, and with an axe to grind. I will carefully study my options and take a decision based on my needs. There are no silver bullets in engineering.
I had to fix a SharePoint workflow that indefinitely kicked off several workflows, and each workflow kicked off other workflows all being stuck in loops. A single workflow could have thousands of workflows kicking off...

Guess who they let make something that simple? Some generic business analyst who left and nobody else knew how to support it.

That second last word there is why developers will never go away.
I wonder, could you talk about the process of getting this published? Was this your first book, did you have a pre-existing relationship with the publisher?
I used to work obscenely late hours in my QA days at Bliizard and I would listen to Art Bell alone in my car late at night outside an undeveloped area of Irvine looking at the hills and the stars at 1am for my dinner break. I still listen to Coast to Coast for 30 minutes every night for the bumper music or more if the topic is interesting.