Hacker News new | past | comments | ask | show | jobs | submit | JodieBenitez's comments login

> - Easy to deploy: Upload files, done.

Sure, it works for simple/less important cases. But it also means that your application code is inconsistent while the files are uploading.

Stop your service, upload the files, start the service: safer.

For a Django app you would upload files and ask Gunicorn to graceful reload... similar, just cleaner.


Most PHP apps use a deployment method where a symlink gets set to a directory with a new version of the code. Because of how opcache works this has no impact on running requests, while new requests get handled with the new code.

Yes, my point really... it's really not "just upload files" like it's 1997.

You can use the same strategy with PHP. Preload all your scripts in opcache. Once you're done making changes, reset your opcache.

In practice, any serious project is likely to be version-controlled. Git pull is generally fast enough that it behaves like an atomic change. (By default, opcache will not reload a file that's less than 2 seconds old.)


I'm pretty sure many PHP dev don't know about OPCache. Many of my colleagues don't know for sure. My point is "be aware of the state of your app code and what you execute", and so be aware of the shortcomings of this deployment "strategy". It's sure perfectly fine and easy for small apps / low traffic / not critical apps. I just want to point that it's not inherently good enough and definitely not the universal way to deploy a PHP app.

Git pull to deploy is something I avoid.


Surprised to see Go in your list though.

Cutting cost: driving creativity since forever :)

> I'm making rapid plans to get the fuck out of this shithole country.

I keep hearing people say that sort of thing in my country in similar situations and yet they never do it.


Good for them. My Australian application is presently sitting in the queue, and I've already had extensive conversations with a number of lawyers about UK and Dutch immigration.


Netherlands: can't you just do Dutch/US friendship treaty, live here for a number of years and then apply for citizenship?


Yes. The downside is the wealth tax, and it can also be very difficult to socially integrate into a country where English is not the first language. (I can learn Dutch of course, but it would take many years.)


My wife is American. Judging by her progress learning Dutch well enough to be able to speak would take 6 months.

It will take her years because she does duolingo for 5 minutes every day and speaks a bit of Dutch with me.

But given by how her progress goes, I'd say it'd take 6 months if you go intensely about it.

Dutch is close to English in vocab.

And by the wealth tax you mean box 3? I don't know how other countries do it but as we currently have it, I find this way more chill than the US. You don't need to log your trades, you don't need to care about capital gains. You'll roughly pay 1% about your net income.

If you want to avoid that a bit: buy art in your house that's stable (if I recall correctly, I'm not a laywer) and your house is your primary residence. So any money that you put into that doesn't get taxed.

We'll change soon to a capital gains system probably anyway, a few years tops, so this point is probably moot.

Again, I'm not a laywer or financial advisor. I sometimes read up on these things, but I'm not razor sharp on it.


What wealth tax concerns you?

Most of the tax begins at $80k+ and then $110k+ yearly income but not so much wealth from my understanding.

PS; The Dutch government may reverse the negative expat changes, especially regarding the special status for capital gains from outside the country in the coming years. And check out Germany. They may also shortly set up a scheme.


You're seriously considering UK over US ? Seems odd to me, that's like choosing only downsides.


Even Boris Johnson can't hold a candle to the imbecility of Trump. And a parliamentary system generally acts as a better safeguard of sensible governance. UK might not be doing great right now, but I feel tentatively positive about the next 5-10 years.

Plus, as a self-employed business owner, I need health care, and I'm not confident that Obamacare will survive the next administration.


I would suggest you prepare to purchase private health care in the UK given the waiting lists.


Regardless, it would be far cheaper than anything in the US, especially if Obamacare gets repealed.


Hhhm, no not really unless you are in the bottom 30% of earners in the US.

You can get US-like outcomes (or worse) on the NHS with the waiting list, or you can get good health care on time with private health insurance. However, you have to pay for the NHS (via National Insurance and higher income taxes) either way on top of private health insurance.

Quality of life and life expectancy/hospital outcomes like Cancer 5 years survival rate, stage of diagnosis are generally worse or equal in the UK to the healthcare the majority of Americans receive. The UK stats are on paper equal or only slightly better on a population basis, but strip out people in the UK with private healthcare or look at it regionally and you will see the sad truth that the NHS has pretty bad outcomes. As in our left wing politicians in power are calling it broken. It is very bad. Really really bad.

If you take out people on private healthcare, there is little difference in outcomes, and you'll be paying the same at the end of the day, just in the UK, without sufficient coverage, options to pay massive sums for the top treatments are often not available in the first place.


What kind of prices for private health care are we talking about? For me, single, in California, the price for good insurance without any subsidies would be around $800/month. And that doesn't include the deductible (~$3000) or copays.

Good luck to you then. You might need it.


I think that to a certain extent the quality of libraries can depend on language features.


Going full OT here but... Yamaha's DX synths had major impact on music. And there are lots of great FM synths nowadays with excellent interfaces. See https://www.twistedelectrons.com/twistfm and https://elektron.se/explore/digitone-ii


Ditto... will probably upgrade when the battery is dead !


Do we finally have a standard solution for input masks ? 25 years ago I was struggling with this while my fellow desktop app devs had good input masks in their widgets, with easy to use pattern syntax. That would be embarrassing if not.


Every other website or program now uses a different set of UI patterns. We are not advancing, we are regressing.

I do miss when textboxes had inset and buttons had outset borders.


Django comes to my mind here. The people behind the framwork had real experience and needs in web publication.


> Just define a bunch of structs, run a query, map results to structs

Congrats, you now have your own little ORM.


No, absolutely not.

Op is never implying they intend to maintain one to one correspondence between the DB and objects and do that through manipulating objects only. Mapping hand written queries results to structs and updating the DB yourself on the basis of what is in structs is not at all an ORM.


> Mapping hand written queries results to structs and updating the DB yourself on the basis of what is in structs is not at all an ORM.

You just described a bad, home-grown Object Relational Mapper.


No, absolutely not. You don’t even try to manipulate the DB using object-oriented concept in this case. That’s just a good old I/O layer used on a need to basis. This is not in any way an ORM by any sane definition of what an ORM is.


Not in most modern web application servers. ORMs seem to solve the problem of synchronizing some persistent application state (like a desktop GUI app) to your database state, but web application servers are usually relatively stateless. It's better to think of the application's job as taking a request, parsing it, compiling it to SQL, handing that to a database, and serializing the results.

Through that lens, the parts where you load and save object state are redundant. You're going to throw those objects away after the request anyway. Just take your request and build an UPDATE, etc. Use record types merely as a way to define your schema.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: