HN user

bartkmq

56 karma
Posts0
Comments30
View on HN
No posts found.

I watched the NASA press conference, where the decision was announced, and Bill Nelson said that the new Boeing CEO promised him he will work with NASA to keep Starliner flying.

It will require quite a significant investment to fix the project, while Boeing is already loosing money on this fixed price contract.

Well, that didn't work too good.

Reword the text below without using the letter a:

[text]

According to every known law of aviation, there is no way bee should be able to take to the skies. Its wings are too small to lift its hefty little form from the ground. The bee, however, flies regardless because bees do not worry about what humans deem inconceivable. Yellow, black. Yellow, black. Yellow, black. Yellow, black. Ooh, black and yellow! Let's mix it up a bit. Barry! Breakfast is ready! Ooming! Wait one moment. Hello? Can you marvel at how quick they fly?

[dead] 8 years ago

This website doesn't look very reliable to me.

  Confirmed: Las Vegas Shooter on Benzos During Mass Murder
  The CDC's Fictional Flu Death Stats and Tamiflu's Lethal Side Effects
http://www.greenmedinfo.com/

For comparison with Alpine Linux:

  base kbd-bkeymaps, xz compressed: 2.8 MB
  base kbd-bkeymaps busybox-extras, xz compressed: 2.8 MB
Just 100 kB more for telnet, no extra deps.

I wouldn't actually want to work in that chroot but for containers it's fine.

You've got good points and I admit I'm split on this issue.

In theory i would rather have everything handled by the package manager but container apps provide a few useful advantages:

  - sandboxing/isolation out of the box
  - being able to report bugs directly to upstream
  - It's easier to distribute a small app to all distributions (for some value of all)*
  - much easier to distribute proprietary applications (subjective advantage)
  - much easier to install old versions of an application (sometimes needed)
  - it's possible to record the bandwidth/ram/cpu usage; with a standard package that's quiet difficult

I can think of a few reasons

(1) Use of a different libc (alpine linux with musl)

(2) most builds are not reproducible, rebuilds are needed for security reasons

(3) non-rolling release distros (-> most distros) fork the upstream projects to backport fixes for their older releases

(4) Different filesystem structure (Gobo Linux)

(6) Most distros want to use the build system associated with their own package manager

There are probably many more than that. Most distros don't even try to stay close the upstream repo and instead maintain a lot of patches.

In the future we will most likely have an distro-specific basic system build and container apps (snap, appimage, flatpak) build directly by upstream on non-server systems.

(1) Nat. Gas causes much more deaths per PWh produced (5 vs 0.1 for the US) and still produces quite a lot of CO2.

(2) Renewable + pumped hydro is much more expensive that just producing electricity directly from nuclear. The environmental impact of dam failures is also bigger than that of an nuclear accident.

For example the Banqiao+Shimantan dam failure killed 110,000, displaced 6,000,000. For comparison Chernobyl killed 9,000 to 93,000 (probably closer to the lower end) and displaced ~130,000.

I disagree. Brave is targeted at the average browser user. Only ~10% of Windows users use adblockers, 2% on Android/iOS.

And you can't tell me all of these people want to see ads, most of them probably just don't know about adblockers (or find them to difficult to install on mobile).

Brave solves that problem because they present a finished solution that simply works for the user.

The comparison between Chromes and Braves (Electrons) internal details may be interested for developers but the average end-user just cares about the speed difference between Browser X and Y as they come out of the box.

Because you need the files to do proof of proof-of-storage and get your coins (back).

But as the OP said there's currently no proof-of-will-to-distribute-storage so you can save money by just sending the proof-of-storages to the network and never actually provide bandwidth for the distribution of the stored data.

What does EFI support mean? I remember booting Alpine on an UEFI system a few months before this update so it can't be support for that. Is it maybe related to efistub?

Does anyone found an alternative to "BackTrack Tab History", an extension that copies the history of the current tab to newly opened tabs? The author thinks he won't be able to port it to Quantum.

He defines 'vanilla' to mean 'build from upstream with little distro-specific changes'. So what does this have to do with making Python 3 the default python interpreter? I bet this symlink is not even part of the python source code; it's always a choice made by the distro maintainers.

Arch is known to be always cutting edge even if this sometimes means breaking stuff so this decision is not exactly surprising.

I'm a big fan of the Arch User Repository (AUR). But Arch itself takes too long to configure and breaks from time to time so I switched to Manjaro which is based on Arch but has its own repos with more config files already prepared for you. Also it's not rolling release but updates once a week which allows the maintainers to check for errors before they reach the users.

Because of the AUR I actually think Manjaro can be more user friendly than distros like Ubuntu. While using Ubuntu I remember constantly having to deal with PPAs which were broken/outdated after every update. On Manjaro I can just hit 'Install' in the GUI and don't have to worry about PPAs. I even found a package specific to my university that sets up the Wlan and other things. On Ubuntu finding such an unknown, rarely used package would be much harder.

This suit is only a flight suit and can not be used for EVA as it lacks a life support system and heat exchanger. That being said their EVA suit will probably look similary cool so you're still right ;)