There is a ton of projects like this, all open source and free to selfhost: Plausible, Matomo, Offen, Posthog, Goatcounter, Umami. Or the built in analytics of the static site host like vercel/cloudflare
Java applets involved running an actual JVM on every client computer, which meant basically doubling the risk surface of the browser... plus you had a completely different UI (that couldn't match the browser UI) sitting inside a web page.
I confess I wrote a bunch of Java applets back in the day; but I can't say I'm surprised they died, and I don't think they'll be back.
>I confess I wrote a bunch of Java applets back in the day
Heh. Nothing to confess. Before the HTML5 set of standards (circle 2008), there were certain things you just couldn't do in the browser with JavaScript. That's why there was space for plugins like Applets, Flash, ActiveX, RealPlayer, etc. I did quite a bit of Flash/AS3 (along with the Flash wasm/asm precursor named 'alchemy') development back in the day. If I was able to do it with JS/HTML/CSS I would have done that instead - but you just couldn't.
It's also about the entire internet & its users, not just threat models on specific sites.
We can't ask the general public to consider threat models and evaluate what sites should need HTTPS or just HTTP. General, non-technical intuition is basically useless for this eval; it's not a good path.
It's much smarter to just make HTTPS the default, make it easy & free for any site to provide it, and then let browsers show big warnings for any site that's not secured.
I did not get the sense that this is a balanced perspective.
The author does have a point that not sterilizing your pet will likely lead to criticism, even though it's a more nuanced situation.
But still — the solution to all of the sourcing problems is "do your research, and get an individual, not a breed".
If there's an actual shortage of adoptable dogs in your area, talk to the shelters about it, and also consider _not getting a pet quite yet_, rather then taking random advice from the internet and telling people to breed their pets.
Personally I'm in France: much less neutering here, but also there's a serious feral cat problem in my village, and also too many puppies. And toxoplasmosis infection rates are massive... it seems like a much more obvious choice to sterilize free-roaming pets, but still many don't.
* setting up LE & an auto-renewing cert isn't too hard, and it feels smarter than paying for a cert the old way, but if you're super-busy with everything else, it may not be worth it, yet.
* setting up LE in a rush is bad. You'll make some minor error, you won't double-check in 3 months that yes, the renewal happened, and you will find out that your site has been hacked from your customers or potential customers (except that no, it hasn't been hacked)
* whether you buy a 2 year cert ("now I have 2 years to set up LE") or do set up LE, sign up for SSL cert monitoring. You can have something like DownNotifier.com ping you directly in Slack when expiration is coming up.
Patients Know Best, REMOTE-only (no physical office). Full-time, with occasional exceptions. Core working hours: within a few hours of GMT -- current IRL span: Costa Rica to Bangalore, sometimes a bit further: I'm currently working from Kuala Lumpur for a month while visiting in-laws.
I post on HN sometimes about work-life balance (more than half of our dev team have small kids), building something that improves life/health, and our culture (collaboration and good communication over competition).
Superb communication skills required -- we all need to be highly articulate, clear, and at ease talking through complicated concepts with each other. Sometimes remote work tools are (nearly) flawless, but with some bad luck you might be explaining something complicated over a choppy connection with a punishing 3-second delay and a marching band in the background.
Skills talking with strangers: useful, but not an everyday requirement.
If you're interested in PKB's growth, funding, profitability, contracts, etc., ask -- our CEO is also active on HN. Or Google us. I'm in the CTO role.
We're hiring on & off in different dev roles, and I'm a bit ashamed to admit that our response rate to CVs is unimpressive; but if you're interested and not in a rush, it's a good idea to get a CV and intro letter into our inbox, and we scan through them periodically. Note that of the positions currently listed, at the moment we're probably looking more for mid-level full-stack engineers than any of the others; our stack is principally Java (8)/JEE-based. We use Docker in production and dev environments, Prometheus for stats.
Bonus points (all positions) for experience in the medical world (as an intelligent patient counts!), as well as some history building things from scratch.
It's abstractly difficult to inform a person that their close family member has died, potentially from violent causes, possibly very suddenly.
But come down this hallway, now, to tell this woman that her child is dead; this is what it will be like. You'll need to change your clothes first; you'll need to practice first; and this is what it will do to her, and what it will do to you.
I (obviously) found this very powerful, and while there's some compromise involved in adding in these carefully-selected specifics, it's worth it.
Jan and Brian were uninterested in VC or business relationships to the extent that they were impossible to contact. There was no address on their website. There were no contact details. They ignored inbound emails. There was no signage on the building. They ignored press emails. But Sequoia knew they were in Mountain View and literally had partners walking the streets doing a physical search for them in order to initiate that contact. That's a pretty amazing effort.
Additionally, Sequoia have an internal tool called Earlybird they wrote themselves that monitored mobile app stores, which is how they noticed that WhatsApp was doing so well despite the fact that it had not taken off in the USA specifically. They relied on hard data collected systematically, rather than waiting for hot Bay Area startups that the VC's friends were using to turn up on their door.
And finally Sequoia had a great name that Koum associated with success.
There's a lot of great info in this video. I love WhatsApp partly because it violates so much received valley wisdom and yet has been so successful.
Patients Know Best, REMOTE-only. Full-time, with occasional exceptions. Core working hours: within a few hours of GMT (current IRL span: Costa Rica to Bangalore).
See my other posts for more depth on work-life balance (& hiring working parents = many of us), building something that improves life/health, our culture (collaboration and good communication, not competition).
Superb communication skills required -- we all need to be highly articulate, clear, and at ease talking through complicated concepts with each other (skills talking with strangers: useful, but not an everyday requirement). Sometimes remote work tools are (nearly) flawless, but with some bad luck you might be explaining something complicated over a choppy connection with a punishing 3-second delay and a marching band in the background.
If you're interested in PKB's growth, funding, profitability, contracts, etc., ask -- our CEO is also active on HN. Or Google us. I'm in the CTO role.
We're hiring on & off -- currently we're on hold for full-stack devs; but our lead frontend engineer is going to be motorcycling up the South American coastline in a few months, so we need to hire someone with a front-end focus.
We need: solid JavaScript skills and you know, the normal front-end skillset; a little behind the times because we need to support IE8+.
Bonus points for JSP experience (the backend is pretty solidly Java-based at present), HighCharts. We're in PoC stage for front ends that build on our REST API (to escape the Java-based stuff entirely).
Bonus points (all positions) for experience in the medical world (as an intelligent patient counts!), as well as some history building things from scratch.
Hi Emil, apologies, we're due for another dive into applications. We do try to reply to everyone, but at present we're small enough (and busy enough) that we run through applications in cycles... so there can be a significant delay.
I'll try to review yours tomorrow to at least get you an initial response.
For anyone else applying - if you have a time constraint (like "I think we'd really work well together, but I need to have a job lined up in the next 2 weeks") then you can contact me directly at cto@ (company domain).
Is a reply really necessary. Granted, when a reply does come through (even if negative), it feels good that you've been noticed.
I'm not sure how the hiring culture has changed recently, but I remember around 8-10 years back, I'd send my resume to many companies. No reply, means they are not interested.
I don't have a problem with them not being interested, just like when dating :-)
But since I am applying to places I only really care about, I'd like to know when I'm not a good fit (so I can improve in the meantime), but mostly because so much tech stuff can go wrong (db died, email got marked as spam, their reply got lost somewhere, etc).
