While i like FFs existence, Mozilla is being disassociated with FF - to me at least.
118 karma · joined July 12, 2020
While i like FFs existence, Mozilla is being disassociated with FF - to me at least.
Disliking corporations and anti-competitive behavior of big corporations seems to be a non-partisan issue; and yet there seems to be much support for making everything ran by massive corporations. I don't understand their line of thinking here.
To the issue at hand though; much of America is embroiled in various angles of anti-taxation. There seems to be wide support for the idea that the government is incapable of doing anything right and any amount of money going towards them is viewed in a negative light.
I think government in America really needs to step up on the deliverables and communication of deliverables. Efficiency likely could be improved, i don't deny, but i also think that the lack of "Here's what you paid for, here's what you got" leads people to think they get nothing for their money.
Regardless of what your personal opinions are of taxes, i think it's safe to say that America has a problem with them - and doesn't know how to solve it. This infighting over mail delivery, a staple of communication, just highlights a deeply rooted issue.
Firing a team building a meaningful advancement in Firefox's tech stack is a big signal, imo.
HOWEVER, i like to write distributed software that i want "uninformed" users to run. Aka not run on nice, automated k8 deployments - but on dirty, random computers.
My current idea is to run this software on all my personal PCs, but also a couple RaspPis over wifi in random locations.
Slow, poor connectivity machines sounds like a decent and predictably bad user environment.
I think the author mentioned only spending $449.73USD (i can't verify because the sites down), which seems cheaper than what you mentioned.
I'm also struggling to find exactly what you're talking about. I'm seeing 9020's, but no M, do they actively sell it still?
I'm not nitpicking your comment - i too am interested in throwing a couple Pis in a closet for some distributed systems projects i'm working on. I expect them to be slow, low bandwidth, but simple over wifi/etc. I don't want to pay more than i need for closet computers, though, so i'm interested. :)
So while i think i will get the VPN, Pocket on the otherhand... is just meh to me. Products where i give some cloud company a ton of data, even if a good company, is just not an interesting problem for an honest company to solve.
VPN is meaningful. Privacy in general is meaningful. Basic necessities like identity and communication are meaningful.
Pocket is a really nice feature and a good UX, but just not interesting to me for the company goals. If it makes them money i'm happy, but it's just mildly more interesting to me than Mozilla Tiktok might be.
I really hope they embrace the essentials to the web, and make a profit doing so. VPN seems like the right direction (though i'm dying for it on desktop). Pocket, less so... to me.
This just feels like an attempt to control who is the middleman spying on data, not actually securing Americans data. Which makes sense, coming from the government and whatnot - but i'm just trying to make sense of if there's an actual reason i should like this "Clean Network" (which is to say, my comment is an honest question, not an attack on the proposal).
Perhaps i'm just biased because of my (pet) passion for distributed systems. I don't trust any MITM, so i think i struggle to understand the concern for _who_ is in the middle.
I'd be far more interested in this type of pitch if it came with heavy support for encryption, distribution, etc.
This makes me wonder - what ads would be acceptable in the eyes of privacy focused developers? Any?
And i don't mean UX - i mean, what ads would you, a privacy focused developer, recommend i install on my site. Assuming i want to fully respect by users privacy, while still attempting to pay for the server costs.
Maybe this warrants a AskHN, but it seems relevant here as they're implementing this exact concept. Thoughts?
SQLx has been really nice so far. I recommend it.
Does vscode-neovim work around this somehow?
Ie, i tried out Diesel for a few projects and after several months, i'm moving away from it. The compiler messages can be insane due to Diesel's rather.. excessive use of generics haha.
Funny how self learning can sometimes mirror what you end up asking in work - even though they're not related at all.
Appreciate the thoughts, thanks :)
So i ask, where do FTS and SQL constraints or implementations differ greatly? Why does Lucene exist rather than having the same features in MySQL or Postgres?
I'm asking in the context of road bumps, things to watch out for - should i try to merge the ideas and implementation of a SQL DB and FTS.
(Note: I am aware that some SQL has FTS, but i imagine it still differs or has weaknesses when compared to a strictly focused FTS engine like Lucene)
I'm a backend dev and, while i can do frontend - and i usually am picky about design, i don't _want_ to design, especially during prototyping.
I'm planning on learning Tailwind for post-PoC styling, but buying the Tailwind Builder (Lifetime) for early PoCs to get styling out of my way.
I really like the offering of not just templates, but transitioning my templates into my final product _when i want_.
But, i haven't used any of it yet. We'll see, but it's definitely worth the $99 license (to me) if it even remotely pans out.
Eg, when you visit a site you, imo - agree to some degree of privacy violation with that site. Ie, it's reasonable to expect them to know your IP. It's reasonable to expect them to know your rough location. It's reasonable to expect them to know your username if you log in, and etc.
What's unreasonable is the 50 sites that cascade off of an initial visit. I may have been fine giving my IP to bobsblog.com but not Google/etc.
An interesting extension of this idea would be a hosting service or web framework that didn't just say something like "no javascript", but rather "no external connections with your information". All images, CSS, JS, etc would be loaded locally and nothing would make any remote connections from your IP.
Come to think of it, this would be a neat "contract" that sites could agree to. Like No JS, such that browser clients could enforce it and get the expected UX on those sites. /shrug, just thinking out loud i suppose.
Really appreciate the reply, that's a great question.
> the gold standard has to be facilitating some way where they can do some actual work with you.
We've actually done this, recently. It worked okay. We identified a few problems with that iteration for us though:
1. We chose real projects, but we felt limited by finding a project where the scope could be small enough for the developer to create it to a meaningful extent and not be bogged down in planning. Projects without meaningful planning however felt so simple that i didn't feel it would challenge anyone. 2. I really hated giving interviews "real" work. Which is to say, it was work we as a company needed - but that felt too easy to be seen as exploiting the applicant - for good reason. 3. I felt disconnected from the applicants mindset. I want to understand how they think on a problem - what things they're skipping for time, what pain points in the application need testing, what things they think need to be abstracted, etc.
I did like how it gave them time to solve the problem themselves. As someone who struggles with.. stage fright (for lack of a better term), interviews are hell for me. I want to hire people even if they're terrified and draw a blank.
My next set of interviews coming up i'm thinking i'll try a combination of a take-home project, but also something pair programmed. Perhaps a take-home, and then we review in a pair program after? I want them to be able to not be under pressure, but i also need some insight on their mind.
Unfortunately i have no idea offhand how to design a take-home that is both simple but not brain dead. I don't want it to take long, i don't want to riddle it with complex algorithm based requirements either. My initial gut is to mock up some requirements - after implementing them myself - that have real world value. How do they choose to abstract database access for unit testing? What do they choose to cache with? Did they consider cache invalidation? Something like this.. i guess.
My final concern is that we'll be hiring for specific languages, but i'd like to be able to hire someone wanting to learn and use those languages. Partially because it promotes growth, but also because it opens the job market. Namely, we're a Rust shop and i don't want to hire only people who know Rust - but i also don't want to hire evaluate someone based on a take-home in another language.
I'm debating offering a pair programming option for the take-home if they're not comfortable with Rust. I would expect their take-home to be far worse, as so many concepts would be new.. so i'm unsure if this would be valuable.
Thanks for the reply, and if you have any more thoughts i'd love to hear them :)
Best of luck on the market!
For some context on my question:
I'm part of a startup-ish group of people who, frankly, don't have a tech hiring group. We have ~25 engineers (i'm losing track these days lol), but no real manager-engineer bridge. Which translates to, we have a bunch of people who code but none who know how to hire. Unfortunately, i am one of those responsible for hiring, and i've got no clue what to do.
We've gone through various attempts over the years. I've been part of ~15 hires for the company - most of our current tech side, to one degree or another. We heavily value hiring the "person" - so we try to suss out people values and cultural fit, but i think we really suffer from being able to evaluate the technical ability of the candidate.
We're not worried about hiring the top talent of SF - we probably couldn't afford that anyway. But we do want bright people who can grow in the problems we're solving. This is where i'm struggling to improve on, as a person hiring.
Thoughts?
I'm interested in writing two main components:
1. Information storage, with retention / etc. My initial feature scope is likely going to focus on retention (spaced rep) and storage (archiving sources), long term i want to dog food a general purpose knowledge base.
2. Data storage. Unfortunately every time i start working on the schemas for the information storage i end up reinventing so many features of general purpose data storage, like versioning, data deduplication, etc - i end up with a clone of Git :(
So i'd love to hear some words of wisdom on this subject. I imagine you - sanely - focus more on #1, but that's not an area i've obsessed about yet too much.
This whole topic does interest me though - part of the reason i'm writing the data layer is because i want a git-like behavior to be able to slice other sources of information up with the ease and safety of git. So the idea of information source interop is close to my hear - but the idea of IO with external formats has not been big on my radar.
As i make progress with the information side of things, i'll have to keep that in mind. My model embraced self-hosting and i really want to avoid information hostage. So this convo has already been valuable :)
Eg, i actually like "current events", especially news. I want to know what my political actors are doing, good or bad - but only concrete information. Especially with the current administration. Rumors / weak leaks are wasted cycles in my brain.
How would tight regulations like that look in a large country already flooded with weapons of all shapes and sizes?
I know multiple pro-gun people who seem to compose a large percentage of their pro-gun belief system around the foundation of the inability to remove them. Ie any bad guy who ever wants a gun will always have it (because there's so many), so give more guns to the good people.
What are your thoughts there? I don't really have a counter.