skysight-inc/HackerNews huggingface dataset:
An ROV-sized unit uses "water-lubricated slide bearings".[1]
Some use ceramic bearings. There's been experimentation with magnetic bearings. Good overview paper [2].

Hydrodynamic bearings running in water seem to be popular. Those have a design which self-pumps water between the bearing surfaces. The load is carried by the fluid, not the surfaces.

The neat thing about this design is that most of the headaches of operating in water become advantages. Water provides lubrication and motor cooling. No oil, no shafts, and no seals, the usual headaches of things which operate in water. There's still corrosion and general marine crud to fight, of course.

[1] https://www.schottel.de/fileadmin/data/pdf/eng/SRT_Flyer_A4_...
[2] http://www.elkraft.ntnu.no/eno/Papers%202004/ICEM04-Krovel-N...
I can only guess - after you cross 25 years of age, I have never heard of insurance going down. I know people who are 50-60 years old, with zero claims ever, and they never get a discount, the annual renewal always come back higher. So what they do? They move every year. Every single year, they go through the effort of calling few insurers to get marginally better price to avoid the inevitable hike.

I can only guess that if you are rich then you don't care - it's more likely you will stay with the same insurer because it's not worth your time to be looking elsewhere.
This is my personal opinion.

Structure wise: Having a singleton app store and separate component states together is the best pattern. Hidden details of a component's functionality should go into its own state. App level data (like the current user) should go into the single app state. Also the minimal set of state that defines the other part of the app state (typically state props from user input) should be two-way reflected in the URL or local storage - depending if its a shareable state detail or user preference.

Timing wise: Synchronous view updates (MobX approach) cost too much performance wise. It is often also not in align with the natural expectation of the developer. (Even MobX has actions, which is just async execution with a bit more granularity). React's approach is a bit too lazy for my taste. Updating the state asynchronously leads to confusion and has no benefit in my opinion. Synchronous state update has practically zero performance cost compared to view updates. Updating the state synchronously and the view asynchronously - but always before the next paint - seems to be the best approach for me. You will never extract existing state from your view and from the user's perspective the only important thing is to have it updated before it is rendered.

Data management wise: I think it is super important for a reactivity library to do not save or alter any of your state. It should just save reactions paired with data mutation/access points. Saving data can cause staleness and mutating your data behind your back is just a mess. I was super careful to leave you objects untouched (opposed to array hacks, hidden getters/setters and memoizing your own getters/setters (computed values)).

In the end Easy State is most similar to MobX. It just saves reactions (renders), which it triggers on state/store mutations. The biggest difference is in its timing (async vs sync), minimal syntax and (in my opinion) fewer edge cases. The difference between using the state vs an external store is pretty much a one line change. They are both normal observable objects, they are just in different locations with different names.

Sorry for the long answer. No worries if you don't have time to read it (:

Edit: I also dislike 3rd party injection libraries (like the MobX @inject decorator). Simple ES6 imports should be enough for injecting the single app state and props should be enough to pass down a component's own state. Angular is a prime example of how more complex injection systems can go wrong. This is just my opinion though and it even might change in the future (:
You don't think that modern CRUD apps do anything besides showing text and labels?
Command line tool for soccer written in Dart Language
Where clause is the worst possible use case for GPU: GPUs don't tolerate branches or non-coalesced memory access all that well, and WHERE executes a ton of branches. Even so, things seem to be faster. Go figure.
VP isn't a bad idea by itself, but its implementations usually have the same problems:

1. It's hard to make a scheme in editor without spaghettifying it. (Partially mitigated by blocks incapsulating parts of scheme in themself, some discipline is required)

2. Usually VP makes it hard to work with complex data structures. The only solution is to basically write the same code as text losing all VP in the process.

http://hiasm.com/ : Very usable constructor for small programs, the only problem with it is that website is in russian.
Just saw this, TL;DR we transfer a large file onto and off of the mSD card. If its above 10MB/s for both (which is the base rating on a class 10 card), then it is a fine mSD card. I've also noticed that on multi-gig files speeds tend to drop to around 6MB/s, not the end of the world for us, but also not a sign of a bad mSD either.
Since when are 150+ layer CNNs fairly standard?

Inception-v3 has about 50 layers, and that's considered a lot (requires considerable processing power to train).
Every time a VPL (Visual Programming Language) has gone against a TPL (text programming language) , VPL not only has come out a winner it has massacred its opponent.

There are 3 areas that I am aware of that VPLs have appeared a) modular audio synthesis b) 3d graphics c) game programming

(a) has been the first with origins back to 1995 , there are like a ton of programming apis for building modular synthesizers , there even programming languages that specialize in this that have existed for decades now like CSOUND and Supercolider but Reaktor and Max/MSP have literally mopolised the market. Reaktor itself has been such a massive success that made Native Instrument as the dominant company on audio software.

(b) 3d graphics is no secret that is probably the richest software industry with the generation of the well knows CGI for films and games its a goldmine for developers and has been dominated by VPLs. You are not aware of this most likely because we never refer to them as VPL but rather as procedural material, textures, animation etc. Not using a VPL for todays standards is considered insane even if you try to do it via a very lovable language like Python. Text languages like POV RAY that specialize in 3d graphics have died a miserable death. 3d is where TPLs go to die and are used strictly for generating the software alone and thats about it.

(c) computer games there VPLs are something new but Unreal has definitely changed that with Blueprints. Probably the best and most powerful VPL. If you have played any kind of AAA game chances are that the game you played uses Unreal which in turn makes heavy usage of Blueprints and C++ code. The rule of thumb among Unreal developers is "Do it with Blueprint and if you cannot avoid it do it with C++". Unity has smelled the roses and has implement its own VPL as well very similar to Blueprints.

So if VPLs are so amazing why we do not see more of them ? They are actually very hard to make. If an implementation of lisp , a basic one, needs a few hundreds lines of code a VPL needs thousands and that imposes a high barrier for language designers. Hence why we have thousands of TPL and only a handful of VPLs.

The majority of them are crappy obviously because that is how quality works , you have to have high quantity for high quality.

But a high quality VPL will kick high quality TPL ass any day and this is why VPLs are massively more popular than TPLs for the same task.

One that does not work as well as it looks and it depends on drag and drop is a crappy VPL . Yes a crappy VPL will suck, not as much as a crappy TPL (see C++ , Javascript etc) but it will suck none the less.

you can also read my quora answer here for more details why VPLs dominate so easily and why they will replace TPLs in the not so distant future to a very large extend

https://www.quora.com/Why-did-graphical-programming-language...
I mean if a book is less than 15 bucks it might as well be free, practically speaking, for most people who post here.
Odd, I've only ever seen this be an issue on the Raspberry Pi platform, outside of that power loss doesn't regularly cause data loss on most Androids or Allwinner boards so long as the mSD isn't of low caliber.
Related is the todo.txt format: http://todotxt.com/
Yeah, not really. With the current state of various spaceguard projects working on mapping NEOs (near-Earth objects), the estimated "heads up time" for an extinction level asteroid impact is on the order of decades. The smaller the object, the less notice we get, but the risk also decreases dramatically.
First I started with screen but quickly switched to the tmux-vim workflow. Then Comodo AV at work killed any chances of upgrading/building from source (long story) so I had to switch back to screen which i hadn't used in years. Now the only thing i really miss from tmux is the panes. screen splits is just not the same, but the productivity gains are still there. Oh and I miss that big clock too! C-b t
If that was true, then Mercedes and BMW wouldn't sell any diesel S-class or 7-series cars, and yet they do(and they are majority of sales of these models in EU) - people want luxury and great fuel economy at the same time.
> I do believe that a better code editor is possible through non-plaintext programming. (Serialize token trees and ASTs, instead of plaintext.)

Funnily enough, this is itself another of those mirages, like visual programming, that have been chased for years and failed to gain traction (outside specialised applications).

For my money, the reason for this is that a human editing code needs to write something invalid - on your way from Valid Program A to Valid Program B, you will temporarily write Invalid Jumble Of Bytes X. If your editor tries to prevent you writing invalid jumbles of bytes, you will be fighting it constantly.

The only languages with widely-used AST-based editing is the Lisp family (with paredit). They get away with this because:

1. Lisp 'syntax' is so low-level that it doesn't constrain your (invalid) intermediate states much. (ie you can still write a (let) or (cond) with the wrong number of arguments while you're thinking).

2. Paredit modes always have an "escape hatch" for editing text directly (eg you can usually highlight and delete an unbalanced parenthesis). You don't need it often (see #1) - but when you need it, you really need it.
Per thermal radiation, does that mean essentially light? So if you see the explosion, no time to get out of the way, already burned?
A real net transfer of wealth only happens if their increase in wages outpaces the increase in costs that they pay because of everyone else's higher wages.

Current costs (at least part of them) are a reflection of the cost of unskilled labor. What impact does increasing the nominal cost of unskilled labor have?

The relationship between costs and labor haven't changed. I don't think it's logical to think that without changing that relationship you've somehow managed to make them wealthier.
Long pig.
Blizzard 2FA doesn't even come up. Having it installed is good enough for automatic detection if on same device if I remember correctly. If on different devices you have to press accept or deny comparing a unique code on the app vs. On the app where you want to login. Much easier than copying the code.
POLL: Morata or Belotti for Milan?
Software

The Mythical Man Month && Design Of Design by Fred Brooks

Everything else

Hitchhikers Guide (Existentialism does not have to be edgy)
The Foundation Series (Bureaucracy and Institutionalization will never undermine Ingenuity)
Dune Series (Plans within plans)
Designed correctly, there is potentially a whole spectrum between "complete success, desired orbit" and "fire-y ball of death". As other commenters here have pointed out, one of the Space Shuttle's fatal flaws is that it severely narrowed that spectrum (even one of the supposed "abort modes" probably wouldn't have been survivable).

So far, everything SpaceX has done is working to greatly expand the window of "survivable failure". Remember on one of the early Falcon 9 flights when one of the 9 first stage engines literally disintegrated and the rocket kept flying? How many other rockets flying today can do that?

So, no, I don't expect we'll see people die in a SpaceX capsule. When was the last time someone died in a Soyuz?
No problem. You weren't wrong!
Show HN: Golossary dictionary – look up multiple words at once
> A military whose first line of defense is nuclear weapons is not a functioning military.

What's the relevance of this statement towards OP? Reducing nuke does not harm US' strategic supremacy at all. The current arsenal is plainly too much...

It's dead simple to reduce cost and still maintain the same strategic position.

But you know what, USA won't do it...
Pretty much, I'd much rather talk with a MAGA than a liberal, despite the similarity in views I may share with said liberal.

The former I can often have a sensical conversation with and perhaps change their mind on some issues, the latter feeling an outright opposition to taking action or altering their views.
You can run Mathematica functions within Clojure. https://github.com/gasc/Clojuratica
I've been working on a project that does exactly what you described for the last few years. IMHO vue.js/react really changed the game here, especially for CRUD apps.

For example what I did was to code a server part in golang and use vue.js on the frontend and for the app builder. Using the web-based app builder (also 100% vue) the user can design forms. The forms are stored as serialized JSON in the database and the server renders dynamically vue.js components. It's super fast.
And there's a complete freedom to design any form with a 16-column responsive grids and a lot of widgets and styling options. Forms are also nestable (thanks vue!) and completely extendable with custom JS code so it's possible to create a custom widget and then simply import it in other parts of the app.

As I said I think the shadow DOM and frameworks like vue really made the difference. I started without using such frameworks and it was not only tedious, but the resulting app wasn't very interactive and felt like a customized Excel spreadsheet attached on top of a PostgreSQL database.
Now it's a completely different story - it's easy to build fully reactive apps that feel like a "normal" cloud app and are actually pleasant to use. Of course instead of spending few months designing and building it, it was created in a few hours.

So yeah... I think that drag-n-drop builders are definitely coming and will probably eliminate the need to write such apps in coming years.
The biggest problem here is multi-device support. Right now you can enter the same email + mpw on a different device and it just works. Adding a local secret means you must manually transfer that to any new device.

Seems like a good feature for people with stronger security requirements (eg, journalists), but not the average user.
I disagree. Given enough money you'll get a top-tier doctor in any specialty pretty soon, pretty much anywhere. Again, my point is that probably few places disallow this service, as you indicated. Maybe you meant to say that even the wealthiest in countries with outstanding health systems don't bother looking for such a service? That may very well be the case.
Jean Sammet, co-designer of COBOL, dies at 89
Think ancient Egyptian hieroglyphs or Chineese pictograms. They seem like a good idea until you need to describe specific nuances. There is a reason alphabet won.
It doesn't. The electrical world has been using contactor diagrams for complex logic for decades, and with the inclusion of more advanced computer components ladder logic (still the same concepts, symbols and logic)

https://www.allaboutcircuits.com/worksheets/ac-motor-control... is the link I quickly found.

It's typical to see a handful of symbols handle what would take a hundred of lines of code for the level of user interface usability, validation, and core functionality.
Think of it this way, would you jump in a luxurious train that can only travel through 10 cities max? Or would you jump in a dirty, cheap and slow train that can go on forever and potentially reach your final destination? Right now you're seating in the 1st class in a local train. You're at the top of the mini-chain. That's what we call the "standard" world. You're dreaming about the "exciting" world, the top %1. When you make the switch you have to jump off the comfy train and you end-up losing your spot. It took you a while to get there. Plus, you'll have to find a spot within that dirty train. Life's tough heh?

People don't like to take risks because they're afraid of making a step backwards. That's where you're are now. The competition starts at an early age, school, college, you want to have the best grades, then your first internship you want to land the best gig in the best company. When you apply you want to work in the best team. But it's really contained within the standard world right? Who defines your goals and your paychecks? People from the "exciting" world. Not you. You can't reach the top %1 because you work for them. You make them what they are. Do it for yourself, be selfish.

You're already going in the right direction, the problem is, you're in the wrong train. Jump off while you're young you'll run fast enough to hop on the dirty train. The journey is long but one day you'll wake up at your final destination. We'll all die one day. You have nothing to lose my friend but a seat in 1st class.
>> That's a bullshit response from Tesla

It's a Chewbacca Defense. At the end of the day the evidence shows Tesla owners should pay more due to the frequency and cost of claims, thus higher rates. Squabbling about whether Telsa vehicles should be compared to luxury SUVs, Bentleys, Lamborghinis or whatever just muddies the water. AAA put the comparison out there so they have only themselves to blame for providing the ammo, but that doesn't actually salvage Tesla's (non-)argument.
You can try emscripten mailing list: https://groups.google.com/forum/#!forum/emscripten-discuss
Because it reduces people to a set of identity classes that fill respective identity checkboxes. I.e. if it happens that on conference there is 10 good presentation submitted from class X but only 2 from class Y, and the quota is half-half, you would either reject 8 good presentations or add 8 crappy ones, just to fill identity checkboxes and achieve equality of outcome. Or cancel the conference altogether.

The true equality would be when the conference organizers see 12 good presentations, and don't even think to dig into what identity class they represent (unless the conference is specifically organized to represent identity classes). When did you last seen statistics about hair color or eye color of conference presenters? How about blood type? Maybe AB- people are underrepresented? You get the idea.
Don't get me started on down-your-throat, manual error-handling; imports tied to repositories and opaque, mandatory N*M-threading; the outright hostility to features like flexible locking. Or the overly draconian package reference rules which turns any non-trivial software into a packaging-puzzle. There is plenty more LOLCODE-worthy contraptions in there...

Look, they even admit themselves that the primary goal was for the language to be easy enough for beginners to not hurt themselves; which is fine if that's what you're looking for; for me it's mostly a no go, since I need more power than that to not drown in the complexity of the problems I'm solving.
side note: why has the ANNOUNCEMENT MD5 checksums and not stronger hashing?
Starcity turning commercial buildings into group housing
As I mentioned elsewhere - if you get in an accident in an old car, you end up with a barely damaged car and a dead driver. In a new car, you end up with destroyed car and a driver without a scratch. I don't mean to be overdramatic, but I would rather have every single part in the front of my car to crumple and turn into dust in a low-speed accident, than get impaled on the steering column just because the frame of the car won't crumple under impact.
Also a native speaker, here.

Seems to me that "guys" can refer to a group of men, or to a mixed-gender group, but not to a group of women. So while it's absolutely the case that it can refer to a mixed-gender group, using it that way is still problematic in that it emphasizes men's membership.
I've worked with mainframe programmers and power users and they clung to their genuine 3270 terminals for good reason. All the emulators and substitutes had issues with keyboard differences and iffy keymapping.
Well, that's not exactly a fair representation. The court found as a matter of law (not fact) that the GPL is an enforceable contract. 12b6 standards require the court to interpret the facts in the most favorable possible light for the plaintiff. The facts, but not the law. No factual evidence is required for the court to determine whether the GPL can be a legally enforceable contract, so the plaintiff-favorable burden of proof has no bearing on the legal conclusion which is the subject of all this news coverage. The decision being made as a matter of law in a 12b6 motion indicates that the outcome of this particular case still remains uncertain, but that the court would interpret any other GPL in any other case as a legally enforceable contract.
Why would Russia attack Sweden? What's the point?
I deeply enjoy how this post uses images to illustrate its points. :)
- if you "see" the flash, thats the last thing youre ever going to see. will blind you.

- thermal radiation is, in fact, light, which travels at the speed of light - but you should not imagine the entirety of the thermal energy to be released by a nuclear weapon to be released instantaneously in a radially travelling sphere. that being said, youre not going to outrun such an explosion. where you are at the time of detonation pretty much determines your odds of survival.
I guess it depends on what one considers to be programming. For certain DSLs (audio, control systems, UIs), it seems to be doing OK. For general-purpose work, I think they will always be less desirable than text. Even after thousands of years, words are still our most powerful tool for recording and sharing new ideas.

Alan Kay's mistake is that a lot of his original work was with Papert on educating children. For early learning, having a visual/physical analog adds value. For professional work, when you already have the concepts down, it just gets in the way.
Postgres can have some write-amplification issues for update-heavy loads where at least one of the updated fields is covered by an index. Famously, this triggered Uber to switch to MySQL. Its impact is noticeable in one of my projects as well -- and it isn't that large (a few dozen million rows).
All of this goes to show that the Unix-haters were right.

The Tenex line of operating systems from DEC had built-in session management in the 1970s. Unix still doesn't have it. All non-trivial terminal handling was kept in user-space. Therefore, programs had to make assumptions that are now hard-coded in their very design.

To this day, the Linux and BSD kernels assume that they're talking to a VT100 with a few frills. The commercial Unix kernels were worse; I used a SunOS tutorial in the mid-90s that started me off on ed (yes, the standard editor; the man page even called it that without qualification) because Sun started out with an older version of BSD that assumed teletypes.

This has had consequences. The major reason why microcomputers took off was because an Apple ][ running VisiCalc could do things that a terminal connected to a mini/mainframe computer could not do.

Here we are, living in the future, where wristwatches have true color displays, and household appliances run webservers, but the correct, macho, hipster-approved user interface would be shamed by an Amiga 1000.

/rant