razzio

Would it be possible to protect the cables with a 'hook line' before and after the actual cable that is anchored in the seabed (if possible)? Ship anchors would get stuck on the hook line before doing damage. Only needed below the shipping lanes.

If ship anchors are able to reach the sea bottom then it can't be too deep. Drilling fasteners in the sea bottom at shallow depths could be feasible depending on the makeup of the sea bed. No idea about the cost to install vs repair though.

Born in the Netherlands with stories by my parents on the Nazi growth and eventually occupation, I sincerely hope that history won't repeat itself. I wish you all the best but fear the worst.

I've used Vite in a simple vuejs project and love its simplicity over webpack.

However, debugging Vue3 with hot-module-reload seems to be broken. The moment HRM changes a source file, the line numbers and breakpoints not always line up and breakpoints. (https://github.com/vitejs/vite/issues/5916). The inability to debug properly is not a minor issue so I'm torn to go back to webpack or disable HMR to keep using Vite.

Other than that, the simplification that Vite brings to the build process is sorely needed. I can only imagine how many developer hours have been lost in dealing with Webpack configuration issues. It is ironic that setting up a web development environment is more complicated than building a basic application. Thank you Vite developers for offering relief :)!

Thanks for the summary. Granted I feel a bit sleepy after lunch but the article doesn't have a TL&DR and after skimming I still felt clueless on problems web 3 is supposed to solve.

I guess its one of those cases where time will show what sticks and what people find acceptable. To me they are all controversial.

LOL reading pt 1 and 2 I had a similar reaction.

The first thought that came after the feeling of horror subsided, is that you can simply create a new wallet for each transaction, or maybe a new one once a day. I felt better after that.

Meditation is just a word. As an analogy you can say that driving a car can hurt you. Well that depends what kind of car, your driving style, the speed, whether you use the correct side of the road and so on.

My personal experience is with 30 years of Anapana and Vipassana that started under guidance in a Thai monastery. Even with Anapana, which is considered quite low risk in terms of 'side effects', the message was that it is always better to practice with a teacher and don't mix different practices. This cannot be overstated enough.

My own dark night lasted around 10 years, even with the guidance. Sometimes my outlook so dark it was impossible to look in the mirror. Over time there was a slow transformation of perspective that is still ongoing today. Less clinging to ideas of good, bad, and especially self. Things just happen and most of the time I can now see that all emotions and ideas around that what happens are created by the mind and constantly changing. What starts to matter more and more is compassion for the situation of others and their suffering.

Meditation is often a transformative process and without proper support and guidance this process can indeed be risky.

The husband dedication to support his wife is totally amazing.

This is exactly what I did.

I made the ROM writable by soldering a CMOS ram chip across the ROM (was it 16KB?) and any write to the ROM would end up in the RAM. A switch selected either the ROM or RAM to read from. On startup simply copy the ROM to the RAM and flip the switch.

From there on you can read/write the original ROM and modify it to your hearts content.

Ah yes that brings back memories. I knew that book inside-out.

I made the ROM writable by soldering a CMOS ram chip across the ROM (was it 16KB?) and any write to the ROM would end up in the RAM. A switch selected either the ROM or RAM to read from. On startup simply copy the ROM to the RAM and flip the switch.

After this operation, using 'The Spectrum ROM disassembly' book the world was your oyster. I modified the ROM routines for reading/writing those little tape drives and bypass copy protection, for experimental purposes of course :)

Yes this is also my 'experience'. In my younger days I spend years backpacking on a budget with only a rough outline of where to go.

To me traveling isn't about visiting different places. It is about opening up to the unexpected. Something we don't do so easily when following an itinerary.

This is a fantastic project and I can't wait to try it out!

One question on the network requirements. The web page says for networking: "200 ms or less, 50 Mbps or more".

How hard are these requirements? For folks like me that can't afford a guaranteed 50Mbps internet connection, is this still usable?

There are plenty of places in the world where 50Mbps internet connectivity would be a dream. Even here in Canada there are plenty of places with a max of 10Mbps. The African continent for example will have many more.

Hope it is okay and not too much off-topic. I just donated. He deserves it for this service!

Fact is that stuff like this can happen. Consider how many variables are in play to determine the final cost of a cloud service it is very much a double-edged sword. Sometimes you cut yourself unintentionally.

So now we all learn from this, I suggest we help him out.

That is an interesting distinction. Laws of physics are clearly a constraint to whatever is being engineered. In software development this sometimes plays a role too, more so on embedded and real-time systems. Real-time systems have a time constraints which is a law of physics and embedded software development has to incorporate memory, cpu and sometimes thermal constraints.

I do consider software for these systems closer to engineering, so you might be on to something. That doesn't mean I'd exclude other software development but the notions of (law of physics) constraints and predictable outcome are important factors.

This makes sense to me as someone educated as an electronics engineer. I've since moved over to software development and on occasion feel it can be called engineering, but more often it cannot.

> building something according to formal specifications within constraints...

Yes this is close to what I consider engineering, but maybe it is better to say 'design something according formal specifications within a set of constraints'. Engineering is a process of design. Does this mean implementation is excluded from the definition of engineering?

Plumbers and carpenters build according to specifications and architects design the specifications yet neither are called engineers.

Software development more often than not has little in terms of formal specifications and design, and as the article points out it is very much a field of change. It also focuses mostly on implementation instead of design. That is closer to what a plumber, carpenter and other tradesmen do.