HN user

mrbig4545

210 karma
Posts5
Comments86
View on HN

"I wouldn't write anything big in <insert language>" is pretty much always a true statement. What changes it is the framework.

I can write a web application in some homebrew <insert language> and it can grow to 40 developers, 1000 db tables and thousands of files. But it would be terrible to work on (I know I've seen it). Or i can write the same thing with a framework, and have it much more manageable.

Realistically, when was the last time you say down and wrote a big application in vanilla <insert language>?

Very interesting. I'm always (ab)using cat for this, and I keep meaning to stop, but I forget. After seeing this I'll definitely stop.

Thanks!

On accident is one of those American sayings that sounds weird to my English ears. Like poop. where did the second p come from???

That said, I think our dialects are merging, (well more likely British English is becoming Americanised, but you guys make all the tv, so that's to be expected), for example, when I was younger no one said "ass", it was always "arse", but nowadays it's nearly always "ass"; except for the older generations.

But, we have the same problem within the UK, in the north, we have three meals, breakfast, dinner and tea. In the south they have breakfast, lunch and dinner. It can be very confusing, especially in films when someone invites someone round for tea, but there's no food and it's 1pm!

so it's mod_perl, but javascript and nginx instead of apache and perl. seems like they've ignored history here, as mod_perl turned out to be a bad thing in the end, people messing with bits they really shouldn't leading to massive amounts of unmaintained legacy spaghetti code messing with all parts of apache.

bearing in mind mod_perl's original use was not for writing applications, it was for messing with apache, for doing the things you can't easily do in the config. but where there's a way, abuse will follow, and before you know it whole apps will be written with this

ah well, those who don't learn from history are doomed to repeat it.

so, while it may seem like a good idea now, you can bet in 5-10 years it will no longer look so clever

I was thinking is there a micro-kernel out there that uses VTx to separate the parts, like protected mode on steroids, turns out there is. Thought I'd share

I don't know about conflicting branches, but sqitch didn't like out of order migrations, even if they have nothing to do with each other. The authors response is for the developer with the issue to revert back to a sane point and then redeploy, which is not suitable if you've spent a hour filling that table with data!

I used to use sqitch. It drive me mad, it wants to do too much. I have got for version control, I don't need sqitch to do it as well. And it doesn't play nice with other developers. If you add migration a in one branch, and someone adds migration b in another, then they merge theirs before yours, you're in for a world of pain whne you try to delpoy yours.

In the end I wrote a replacement that did was I needed in under 100 lines of perl. DB management should be simple. No point over complicating it

Not forgetting the guy who writes it is not that friendly, we sent a patch to change the default answer to revert to no, instead of yes. First off he said it was useless, then after some prodding over several months he copied it in and committed it in his name, no mention of where it came from. Real classy

WebExtensions FAQ 11 years ago

I am looking forward to this. The way I see it, it's all preparation for servo.

And I'm sure the extensions to the webextensions api will provide enough to do what needs to be done

It doesn't mention addon permissions, which I would assume is something WebExtensions has, since that's how addons work in chrome. At least I hope this is the case, lack of permissions in firefox addons is a little scary, and probably one of the reasons I have the minimum addons installed

Anyone have more info on this?

Cameron doesn't want to ban encryption. he wants encrypted end to end messaging services to have backdoor keys for the security services use. which is stupid, but very different to banning encryption.

Don't get me wrong, I'm not in favour of this, but the distinction is clear and false misinformation isn't going to help prevent this.