Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MoonHome: Remote Development Environment

moonhome.io

Post reply on HN
Print view View original

81–90 of 97 posts

Re: MoonHome: Remote Development Environment

#81

Post by freemint »

d33 wrote: post #79
freemint wrote: post #74

Earlier quoted context omitted.

> What is your agenda? I just like Hetzner a lot and instantly recognized the pricing hardware tiering structure. I was a bit suspicious how the could sell it cheaper per month as Hetzner (which excited me) until I noticed that by monthly they mean when you shut down your machine every night. I also couldn't find anything on their website that says where they are hosting it. As I like Hetzner fan I am sad that there…

I ran a little code on this comment: >>> sorted({w: comment.split().count(w) for w in comment.split() if comment.split().count(w) > 1}.items(), key=lambda x: -x[1])[:3] [('I', 9), ('Hetzner', 7), ('that', 7)] 7 sentences, 7 occurrences of "Hetzner". It really does read like a CEO-optimized advertisement.

Doing my best? Do you have some suggestions for rewordings? I am not a native speaker, so you are welcome.

Re: MoonHome: Remote Development Environment

#82

Post by KronisLV »

freemint wrote: post #77
KronisLV wrote: post #61

Earlier quoted context omitted.

Actually wondering about this as well, currently considering making my own SaaS, though it's not like there's that many approaches to do billing. In my eyes, a pretty good option would be to automate VPS provisioning and allow each client to order a particular amount of resources, with the software installed on top of them. That way, multi tenancy can be limited to services that handle provisioning, billing and setup…

There is not and if Hetzner would have been mentioned on the website I wouldn't have done detective work to find out it is hosted and I wouldn't have written any messages. Maybe there is something with branding that they can't tell they run on Hetzner but then they should work that out with Hetzner orbtgey are trying to hide. Anyway I saved people a registration and possibly renting an instance to figure out where th…

> If you are mostly reselling compute and storage be transparent where you get it from.

Genuine question: why or why not?

If someone is reselling compute with very few changes and wants to hide where it's sourced from, then i guess it's understandable from a business perspective but at the same time could indeed be considered dishonest. Is that your reasoning?

But at the same time, if someone is reselling compute with custom software or non-trivial automation around it, then i guess the software/automation itself is the product, in which case the compute is just a means to an end? At least in my eyes, if i'd be buying services from something like Mailgun, or something like Heroku, i might not necessarily care that much about where it's running from (except for maybe caring about latency). Would you agree with a statement like that?

Doesn't it all seem a bit blurred, where to draw that line of what's okay and what isn't? Is reselling compute without references to the underlying host/company not somewhat common?

Re: MoonHome: Remote Development Environment

#83

Post by danparsonson »

everyone wrote: post #68

"Modern notebooks prioritize pretty screen and battery time. And when you do need some more computing power you end up with hot casing and laud fans. It is no longer a pleasant experience. " I guess they mean modern mac notebooks

And presumably 'loud' not 'laud'

Re: MoonHome: Remote Development Environment

#84

Post by wongarsu »

pjmlp wrote: post #59
gtirloni wrote: post #57

Earlier quoted context omitted.

Is that good or bad?

Bad, we just go around in circles, with the browser replacing green phosphor terminals.

But how do you know that reintroducing the mainframe model is the mistake, not that we completely got rid of it?

Or maybe the total dominance of personal computers was an intermediate state caused by the low availability of good enough network connections

Re: MoonHome: Remote Development Environment

#85

Post by wongarsu »

smackeyacky wrote: post #40
avidphantasm wrote: post #24

Hey guys, there are these things called “workstations.” Have heard of them?

Yeah, I don't understand the thinking behind this product when you can buy a recently decommissioned Dell, HP or SuperMicro server with a pile of memory and a couple of fast Xeons in it, load up your Linux of choice and go to town with QEMU. This beast here has two ethernet ports as well, so one is dedicated to the I/O for the QEMU VMs and they appear on the local network as actual machines via a bridge. Stick an old…

Whenever I ran the numbers, decommissioned servers were hard to justify. They are cheap to buy, but you pay that back quickly in electricity. And if you want something that's not incredibly noisy you pay a decent premium for that.

Re: MoonHome: Remote Development Environment

#87

Post by hakube »

freemint wrote: post #26

I find the pricing structure surprisingly similar to Hetzner Cloud. There are the same RAM and CPU core tiers running the same AMD EPYC 2nd Gen (one to one and onto mapping). Except prices for storage is almost double. And hourly costs are higher which is kinda hidden by not assuming 24/7 operation compared to Hetzners monthly pricing. You will pay less with Hetzner as they also offer hourly billing. More smoking gun…

You know, he could be using a dedicated server hosted on Hetzner.

Re: MoonHome: Remote Development Environment

#88

Post by playpause »

dreyfan wrote: post #17

This is a really rich description of a completely standard VPS.

A remote dev environment is just one of many use cases for a VPS. They're not the same thing at all.

My brain just isn't good at servers. I have set up many generic cloud servers over the years, but I always hate doing it, it takes me ages to get it right, and I find it hard keep track of everything once set up, and I'm always worried I might have set up something wrong and end up with a security hole or a runaway bill. If I was looking to set up a remote dev environment right now, I would be far more inclined to spend a few dollars per month in overhead for someone to hand-hold me through the process, by providing a clear and simple pricing structure, docs, and support, all narrowly focused on the use case of remote dev environment.

If you're someone who is comfortable playing around with servers, then it makes more sense for you to go lower-level and just set up your own VPS, as you'll probably value the extra freedom and flexibility. For many developers though, that flexibility isn't worth it for the extra complexity and time it takes.

Re: MoonHome: Remote Development Environment

#89

Post by pjmlp »

wongarsu wrote: post #84
pjmlp wrote: post #59

Earlier quoted context omitted.

Bad, we just go around in circles, with the browser replacing green phosphor terminals.

But how do you know that reintroducing the mainframe model is the mistake, not that we completely got rid of it? Or maybe the total dominance of personal computers was an intermediate state caused by the low availability of good enough network connections

When your data is in someone else computer, it is a big mistake.

Re: MoonHome: Remote Development Environment

#90

Post by dreyfan »

playpause wrote: post #88
dreyfan wrote: post #17

This is a really rich description of a completely standard VPS.

A remote dev environment is just one of many use cases for a VPS. They're not the same thing at all. My brain just isn't good at servers. I have set up many generic cloud servers over the years, but I always hate doing it, it takes me ages to get it right, and I find it hard keep track of everything once set up, and I'm always worried I might have set up something wrong and end up with a security hole or a runaway bi…

You don't have to setup anything whatsoever for VSCode Remote-SSH. You give it an IP and user+pass/ssh-key and it takes care of the rest.
Post reply on HN