MrOwnPut

I don't have any questions, but I would like to work for you, love the project.

I will contact you...

I believe due to CORS and native code being used you would need a service to download NPM packages and compile binaries to WASM.

You could offer self hosting of those and no licensing for commercial products, but you then wouldn't have a financial strategy to develop the technology in the first place. Not quite as much at least.

A big draw is you don't have to give access to a 3rd party all of your code if the technology is client side. Since the server side is just managing/proxying 3rd party dependencies.

All that being said, I'd appreciate a more forthcoming statement of this, as it is confusing, bordering on misleading.

I love the technology though and I do have plans to use it.

> you just need to ensure all that get a dose die.

I believe they were asking specifically that. How do you ensure that?

In other words, how do you ensure all get the correct (lethal) dose?

Some may be partially hit. It would be very hard to tell, no?

Err yes you're right on that.

My point though is the "bearing failing" is too generic to determine what on it failed.

Sometimes the brakes are fixed to the axle, are they not? In that case it couldn't be the brake.

> ECP brakes would have saved the day

Citation needed.

It sounds like all administrations (especially those currently in charge) deserve criticism for not focusing on the correct regulations for train safety.

Requiring something that isn't needed doesn't help... It can hurt as it takes resources away from actual necessities, like sensors, and tighter maintenance inspections.

No it would not have, as another posted, the NTSB has reported this was a bearing failure[1].

Bearing failures account for 5.9% of all train derailments[2].

It's possible to help prevent this (not fully as many things derail trains) with more sensors[3] and tighter maintenance checks.

This was most likely due to a lack of maintenance.

[1] https://www.ntsb.gov/news/press-releases/Pages/NR20230214.as...

[2] https://www.wisnerbaum.com/blog/2016/september/the-most-comm...

[3] https://www.southampton.ac.uk/engineering/research/projects/...

That doesn't mean it was the brake. The bearing contains the brake. The axle contains the bearing. The train contains the axle.

Not enough information to determine what caused the bearing to fail, bearing failures account for 5.9% of all train derailments[1].

Though we can look at common train bearing failures to get a likelihood...

Most likely it was a simple lack of maintenance. It's possible to prevent this with more sensors[2] and tighter maintenance checks.

[1] https://www.wisnerbaum.com/blog/2016/september/the-most-comm...

[2] https://www.southampton.ac.uk/engineering/research/projects/...

Yes I agree, that was my point. Though I was comparing train derailments overall, not chemical spills. Chemicals are needed for society.

Nationalizing trains will not help. Nationalizing chemical transfers won't help either if it's the same EPA in charge that said 9/11 debris was safe or this spill was okay.

Heavier regulations on trains may be needed, especially when transferring hazardous loads, but nationalization would be horrendous.

All that be said, investing in pipelines is a much safer form of transfer for these chemicals. Trains are too risky.

Airlines are regulated heavily and safe without nationalizing / seizing ownership.

So a guess then, that's disappointing. Generally things don't burn 100% perfectly.

Unless you were onsite testing what was in the runoff and have the results, you're speculating.

Interesting, do you have details on that, or is that a guess?

Agreed on not losing your mind, that's never good to do, but downplaying it is too far on the other scale.

Seems too early to tell doesn't it? I don't think you can safely say "it would hardly register" without knowing the results from the contaminated regions...

--

Water Runoff

Responding crews discovered contaminated runoff on two surface water streams: Sulphur Run and Leslie Run. Under Ohio EPA oversight, Norfolk Southern emergency response contractors installed booms and underflow dams to restrict the flow of contaminated water as well as contain and collect floating product.

U.S. EPA took water samples at the streams and has sent them to a laboratory for analysis. Emergency response staff noticed impacted aquatic life and notified the Ohio Department of Natural Resources and the U.S. Department of Interior. Ohio DNR is on site and is assessing the situation and the impacts to aquatic life. Downstream water utilities were also notified.

For those interested in using Lua or a similar syntax I curated a list of typed Lua-related projects:

- https://luau-lang.org (Lua derivative, interpreted / sandboxed, from Roblox)

- https://terralang.org (Lua JIT compiler)

- https://nelua.io (Lua-syntax -> C compiler (WASM too w/ Emscripten)

- https://github.com/pallene-lang/pallene (Lua AOT compiler)

- https://github.com/teal-language/tl (Teal -> Lua compiler)

- https://typescripttolua.github.io/ (TS -> Lua compiler)

- https://github.com/sumneko/lua-language-server (IDE only typing)

With minimum effort you can get a lot of benefit from using Sumneko's Lua language server in VSCode for near many Lua versions (LuaJIT, PUC-Rio Lua, etc.)

All of the projects serve different purposes, whether you need/love Lua for speed (JIT, for games), low memory usage (AOT, for embedded), or simplicity (all of them).

Normally yes, but keep in mind if you use pure black/white on a scrollview it will lag the screen and look choppy.

OLED has a delay when switching pixels on and off.

That being said, if it's static please offer a "high contrast dark mode".

Nothing looks better (and more battery efficient) than pure black on an OLED.

(2010) The fix, Bitcoin patch 0.3.10, was implemented by Satoshi

https://bitcointalk.org/index.php?topic=827.0

You can swap out my examples for anything really.

The point is the more work the server does, the more data you have to send them to do that work.

As far as trusting it's client-side only, opening the network tab in devtools would suffice.

If you think they broke the sandbox (Google would pay millions for that!), yes sniffing would be the next step.

At least you have a sandbox on web, you usually don't have that for native apps.

But that's all better than willingly sending data to another entity's server and trusting them to not abuse/leak it.

So lets say a resume generator website, or a document converter, etc.

You trust uploading your personal information to a server to generate the pdf/image/whatever vs doing it in solely in the browser?

Doing more on the server would lead to more tracking, not less.

I love there's no reference of that in his wikipedia article directly, but it appears 3 times in the referenced source titles:

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

Out of curiosity, why do you believe it's not Robin Gunningham?

That seems to be what https://en.wikipedia.org/wiki/Banksy suggests, and the reasoning seems sound.

That's nice if you have the funds and time for that. Fully native is ideal.

But I don't agree cross-platform can't feel "right". Flutter's approach it can't. React Native's it can. Qt vs WxWidgets all over again.

If I had to duplicate my codebase for each platform and learn each IDE/language just to continue my app, it would never exist.

I solely created and maintain the iOS app, the Android app, and the web app for my company and for my side projects thanks to React Native.

I can extend any native api or view, I can learn middle out for each platform.

I can abstract and swap out any file or conditionally style based on platform.

I developed the web app first using React Native Web. It took me a month to get the iOS and Android app released to the store.

No Ionic or web wrapper crap needed... The one thing is getting the React stack and tooling just right.

So it's Expo or devote quite a bit of time in the beginning to your stack.

That's a pre-optimization. React Native Web has been very performant for all my real world use cases.

I'd rather a small perf hit than have another code base for web. You get web for basically free when making a RN app.

That is for APPS you want your WEBPAGE to perform better, don't use a SPA, use Astro or something similar.

Might as well do everything in Assembly or C because it's faster right? Same argument. Development speed matters too.

Why did I have to scroll this far down for the real answer?

This is the true power of the VDOM, to abstract the view from platforms.

Why be a web developer when you can be a cross-platform app developer?

That's why I don't use Svelte and other web SPA frameworks...

As an American, the "down" slang sound weird.

The most I've heard in the wild is a short "I'm down.", you wouldn't say "I'm up." (unless you're saying you woke up, or you're high, or your gambling is going well)

Other than that, your versions are more common in the US as well, from my experience.

edit: Thinking more on it... "I'm up for that" would be used if you were slightly hesitant. "I'm down for that" implies a lot more confidence.

A structure burns down (to the ground). Anything else (including people) burns up.

"The house burnt up", is not proper, but people say it and everyone knows what you mean.

Then there's the saying of what you're referencing, "burning up" as in you feel like you are "on fire", when you are sick.

Phrasal verbs are probably the hardest part of being fluent in English.

People will understand what you mean, but it won't sound right.

GP said "unpredictable" spelling, not complex. And I said "Old English".

I was saying it's unpredictable if you include Old English spelling and words (which you don't in Simplified English).

The remaining unpredictable words are imported foreign words, usually French.

> For some reason Japanese culture is quite popular among nerdy types (be it anime? games? sushi?).

It's popular among all types, very much so in the states and France due to anime.

But they export A LOT of culture. and they are very good at streamlining that export. Fashion, video games, anime, food, etc.

It's really no surprise it's popular. If you end up consuming the culture (as many of us did as kids) you will be attracted to the origins of it as it contains many elements of the culture you consumed.

But yes, there's a lot of cross over between "nerds" or "otaku" and Japanese culture exports.

I assume because they didn't fit into their home culture fully, so they found escape in another foreign one that was adapted for them, and thus found a community to share common interests with, which reinforces that "obsession".

tldr: you can nerd/otaku out on anything, but Japan makes some good stuff to nerd out on, so you get hardcore fans.

English writing can have unpredictable spelling mostly due to imported foreign words (looking at you French!) or inclusion of Old English.

imo that's better than having a whole other system like Katakana to import foreign words.

There's many different approaches to typed Lua:

- https://luau-lang.org (interpreted / sandboxed)

- https://terralang.org (JIT interpreted)

- https://nelua.io (Lua -> C)

- https://typescripttolua.github.io/ (TS -> Lua)

- https://github.com/teal-language/tl (Teal -> Lua)

- https://github.com/sumneko/lua-language-server (IDE only typing)

With minimum effort you can get a lot of benefit from using Sumneko's Lua language server.

So tech here doesn't gain traction unless the average Joe already uses it?

And Brave and NextDNS aren't popular enough for your threshold?

Handshake is exactly what would stop the issue happening in TFA, yet everyone ignores it here.

For something to go mainstream, you have to talk about it...

HN is not a very good tech site if you only talk about the tech that the common person already knows about.

It's been working... for awhile now. But no traction here because... crypto = bad.

There's Handshake, ENS, and UnstoppableDomains.

Brave supports .eth domains out-of-the-box, hopefully Handshake soon.

For Handshake you can use a local resolver that reads the blockchain or use NextDNS.

NFTs aren't just for art, y'know. They have real [digital] world use cases for ownership, like DNS.

Wow, amazing stuff. I love Lua, it was how I learned programming as a kid. Coincidently from the same world as the author. Open Tibia.

The author made a custom client (https://github.com/edubart/otclient) for the game that is still very much in active use by thousands of players. He's a very skilled developer.

Great to see AOT compiled Lua, I know of the other solutions: Luau (from Roblox), Teal, TypeScriptToLua, Terra, etc., but this one is my favorite so far.

Love the simple compilation to C (and WASM support via Emscripten). Though Terra's JIT is enticing and good replacement for LuaJIT, this is for embedded systems, it's a good replacement for Lua PUC-Rio.

Typed Lua Projects:

- https://luau-lang.org/

- https://terralang.org/

- https://github.com/teal-language/tl

- https://typescripttolua.github.io/

There's also a language server for Lua dialects for type checking in the IDE:

https://github.com/sumneko/lua-language-server