HN user
Name me a case where it was crucial to advancing serious and healthy scientific discourse by comparing one of the researchers a molester. Why would that ever be necessary?
It’s a good use case and the one that got me started. I also have a raspberry pi acting as an exit node in my home which is useful when I’m at the coffee shop or in a hotel.
Not just terminals — I have done videoconferencing via that exit node, and I’ve even worked in a “hybrid” mode where some services are on a tailnet, others are on a company VPN, as we haven’t migrated the company over fully.
I don’t have high expectations for actual screen sharing a la VNC or whatever, but it does work, and my lowered expectations for how well I can work that way not specific to Tailscale.
I used to have the similar service on a 2016 Volvo station wagon.
But the radio module in that car is 3G, and because carriers have been discontinuing 3G Volvo cannot provide their service to my car.
There was roughly 12 months when it was impossible to upgrade the radio in my older model car. Now the radio upgrade is customer-paid and optional.
My point being, if they require the subscription I’d be careful to confirm the service is guaranteed regardless of the carriers and obsolete radios etc.
We're serving git over https using apache2, where apache handles authentication via LDAP. We also serve subversion repos with a similar setup. We use separate web services for search, code review, CI, and issue tracking.
Running this way does involve more moving parts, but every part is relatively self-contained and we can replace one thing without disrupting everything.
[Edit] one other benefit I should add, all the other services like code review and CI are compatible with git and svn, so the development teams have consistent tools regardless which vcs they're running for a particular project.
“Being able to look someone in the eye instead of their navel” is a crude caricature of introversion. It’s exactly the sort of misconception that causes people to assume introversion is a negative trait.
For me it’s rarely software obsolescence that prompts the upgrade. My 2014 MacBook and iPhone 6 were retired due to the battery…
I use the Backblaze client on laptops and desktops, and B2 for NAS backups. No complaints.
Surprised to see nobody calling out ffmpeg as one of the most hostile UIs anywhere
You can also join the Meet in a browser, then under the option memu (...) is “Use a phone for audio”. In that user flow the meeting calls your phone and when you join your devices are linked such that the command-d hot key in the browser will mute/unmute your phone mic.
Tycho also works for me when I’m in that sort of mood.
“Since you know the tech intimately, you’ve probably got a solid deployment strategy that you can easily repeat and debug.”
That’s not necessarily the case though. Just as easily I can imagine the opposite might be true.
I say hi to people on San Francisco, but I don’t get discouraged if some don’t respond. There are all sorts of people with wildly divergent circumstances. I’m not or rushing to reach a conclusion about others (or about the overall fate of the city) just because some people don’t say “hi” back.
For those not familiar with the visual effects platform:
With the recent tax law changes, though, I believe a majority of people end up taking the standard deduction because they can’t come up with enough itemized deductions to exceed that. The inability to fully deduct state taxes is a big one, for example.
Strawman argument.
Who is saying the goal is “zero deaths at all costs”? I see governors seriously weighing the costs and risks, and talking about the response when (not if) reopening leads to new flare-ups.
Whitmer: “As we start to very shrewdly reopen (edited: autocorrect) sectors, we’ve got to measure every step of the way. If we start to see a spike, we have to be nimble enough to pull back...”
Newsom: “As we move into the next stage of reopening, we will do so with updated guidance to help qualifying businesses make modifications needed to lower the risk of COVID-19 exposure to customers and workers. Californians should prepare now for that second stage of reopening...”
Cuomo: “This is not a sustainable situation.” However, “You see that you reopen too soon or you reopen unintelligently and you can then have an immediate backlash.”
And so on. I concede there may be someone out there arguing for “zero” but I don’t see the goal of even the more aggressively locked down US states being “zero”.
No surprises there. Just yesterday, I saw someone comment online that a particular opinion article was poorly researched and written like an amateur. Where the author has a Pulitzer and a Gerald Loeb Award with decades in the business at major periodicals and newspapers. It seems clear the judged "quality" of the opinion has mostly to do with whether the reader agrees.
Yeah, but the problem is those api responses are only 95% accurate...
—
TARS : [as Cooper repairs him] Settings. General settings. Security settings.
TARS : Honesty, new setting: ninety-five percent.
TARS : Confirmed. Additional settings.
Cooper : Humor, seventy-five percent.
TARS : Confirmed. Self destruct sequence in T minus 10, 9...
Cooper : Let's make that sixty percent.
TARS : Sixty percent, confirmed. Knock knock.
Cooper : You want fifty-five?
I'd assume what makes alternate ports rare is the fact that the entire implementation is in elisp. So any alternate implementation has to start by finding (or implementing) a parser with good compatibility and maintainability.
Considering mobile isn’t it “all but two”?
The ridiculous part is that the law existed prior to his acquiring the property. He could have (and arguably he should have) known his obligations ahead of time. Even if he didn’t understand the California law, at the very least he could have questioned the existence of easements for coastal access and/or the possibility of some kind of “squatter’s rights” on the grounds that surfers and beachgoers have been using that path for decades.
No, I’m not buying that this is an unfortunate surprise for him. He picked this fight intentionally.
I would say the fallacy is the author's assertion that studios don't know about realtime techniques, or that they aren't already applying motion capture and GPU renderers internally.
Obsolete editions of "Java: A Beginner's Guide"
I deal with that by keeping the separate logical commits, like you said, and I squash only the commits that don't add any historical meaning (like "fix a typo" or "forgot to update the changelog"). I put the issue number in the comments so you can view the history and see a group of commits are all related to a single issue.
Git tracks the committer and the author separately: you should see the “who merged” preserved as the committer and the “who wrote it” as the author.
If each commit notes the issue number in its comment (“Add indentation and trailing white space check to CI [#123]”) then you can see easily when each merge occurred by issue number.
Additionally in GitHub there are conveniences built from these little conventions. The “#123” is displayed as a hyperlink to the issue, and merging a commit that has “Fix #123” automatically closes the issue.
In cases where a feature is big enough to justify multiple commits for clarity, you can mention “#123” in all but the last commit, and “fix #123” in the final commit. Doing so partitions the linear history.
In fact, if someone else notices and fixes a regression caused by the merge, they can push additional commits later on but mention “#123” in their commit as well for documentary purposes. Seeing downstream commits “out of sequence” but with some earlier issue number is a clue this was probably a regression.
Suppose you have an open source or hobby project.
The Free Edition has limitations that impact how you would write code -- it supports only the "peer" API and not the "client" API, and is restricted in terms of backend storage choices and number of peers. So while it's very likely true there's perfect API compatibility when you want to step up to a paid edition, it makes you design to the artificial limitations they've used to set apart "free" from "paid".
Indeed, it's also not the recommended way to learn. The Datomic team says: "If you are trying Datomic for the first time, we recommend that you begin with a client library." In other words, the Free Edition doesn't include the client library that they recommend you try first.
If you step up to the Starter Edition you have full functionality and free updates but only for the first year. Beyond that, you start paying. Either you run in Cloud (as low as $1/day) or you purchase the on-prem Pro Edition ($5000/year).
Don't get me wrong. Cognitect has the right to charge whatever they like, and bundle features however they like. It's their intellectual property and they made the investment to create it.
But if you're building a hobby project then even $1/day may be more than you want to spend, and/or more than you want to impose on outside contributors to your codebase.
Take a look at the recent affordable housing legislation passed in the state assembly and signed by the governor. Can you guess who opposes these measures?
Used in the implementation of a production raytracer at Dreamworks Animation:
It can’t be literally true learning Clojure did you no good... You do need to be conscious in your interviewing, and make sure you have some talking points ready to explain how clojure sharpens your thinking and applies to other languages besides. At that point if the recruiter doesn’t see the fit, you probably want to avoid that employer anyway.
Well, look at the home page for Atom. It describes itself as "a text editor that's modern, approachable, yet hackable to the core."
They then call out features like cross platform editing, a package manager, smart autocompletion, file system browser, multiple panes, find and replace, themes and customization. If this list defines what they mean by "modern" then Emacs has been modern since before modern was a thing text editors needed to be.
However "approachability" is the one characteristic that stands out because it's subjective and that's telling. I would guess most people who aren't already familiar with Emacs find it daunting, just a little bit too different from the rest, and I can see a natural reluctance to invest time in learning something so different if the outcome (how productive will I be?) is unclear.
Are you nuts? Without gravity waves how am I supposed to move the hand of my kid's watch in morse code, and transmit critical scientific data from beyond the event horizon of a black hole? And that's just the practical stuff we already know about... who knows what we'll come up with in a few years? :)