HN user

thirdlamp

79 karma
Posts0
Comments28
View on HN
No posts found.

but it doesn't make sense to allow multiple devices per number anyway

Why not? This is a useful behavior that is currently emulated by forwarding calls to laptops and tablets with the same account when the devices are on the same Wi-Fi. You could get rid of the Wi-Fi requirement if those devices all simply had an eSIM with the same number.

Hydrogen will not be a threat to any electric personal vehicle simply because it’s 3x less efficient (electrolyze water to split it) and thus 3x more expensive to run.

Yayagram 5 years ago

On top of the points others in this thread have made, I think this is also a lesson for UX designers. It's really obvious how the Yayagram works and how to use it and this is how our UX should be.

Many things are moving to the browser, I wouldn't be surprised to see CAD or video editing running in a browser. They could then be OS agnostic, collaborative, introduce some kind of versioning instead of the project_v3_final.psd chaos.

This could be something more like a planetary gearbox or a differential that can connect 3 systems (e.g. gas engine, electric motor, wheels in a hybrid car). But if requirements are too different 2 generators may be the better option.

The tower would probably need reinforcements for the additional weight, but I have no idea about the magnitude required.

Location: Frankfurt, Germany

Remote: Yes, not required

Willing to relocate: Yes

Technologies: Good at Java Backends, open for mostly anything

CV: 3 years backend & some minor frontend (more info on request) and some non-software before that

Email: see profile

Judging by the timeline on https://www.myshiptracking.com it looks like something that would be called pilot induced oscillation in aviation. Obviously speculation on my part, could be that loss of power weakened control authority over the ship and it became hard to manoeuvre.

The ship comes around the curve travelling north close to the outside (right, east, starboard) shore then overcorrect to the west shore then overcorrect more gravely to the east again and run aground.

While we're not in the hundreds (and I don't know our loc), what I've seen happen is that on top of having a large number of services you end up with "meta-repos" that contain infrastructure-as-code or you end up having a repo from which you build the company wide Jenkins image with its configuration and so on.