Sure, but that shouldn't be a time-dependent charge. If my build takes an hour to build on GH's hardware, sure thing, charge me for that time. But if my build takes an hour to build on _my_ hardware, then why am I paying GH for that hour?
I get being charged per-run, to recoup the infra cost, but what about my total runtime on my machine impacts what GH needs to spend to trigger my build?
Interesting. I'm somewhere on the aphantasia spectrum, but I very rarely have vivid dreams. Most dreams I would describe it almost like remembering an audiobook instead of a movie.
But I do occasionally have a vivid dream, and though I can't be certain I could swear that I remember more vivid dreams as a child/early adolescent. But by the time I was entering college I rarely remember my dreams and the ones I do remember are like those I described above with little visualization.
It's really interesting to hear about how others perceive these sensory experiences.
I interpreted it as more of "concepts" and not the word floating in space. That's closer to how I would describe my experience. With effort I can kinda force a static visualization but for lack of a better explanation it feels almost like a wireframe pre-render. Sounds similar to how you describe it.
Dreaming feel reminiscent to what an Audiobook feels like when thinking about the dream after waking up.
LASIK is well known to only be a short to mid-term solution. The eyes age like the rest of you, and any correction will eventually be outpaced by the natural weakening of your ocular muscles to the point where you can no longer pull focus and require glasses. Further correction is possible, but from what I remember being told by my doctor and my own reading, the bounce-back from the surgery is rougher as you age.
I know a few folks from college who got it done and a bit over decade later they're going strong. My own surgery is just about hitting a decade (couple of months shy). That said, I have a family friend who had bladed LASIK done in their 50s (late 2000s) and their outcome was bad with total loss of sight in the affected eye. The result on their other eye was barely an improvement but plenty of scarring lead to halos and starbursts.
I elected for LASIK as my near-sighted prescription was severe enough that I could only see about 6-8 inches in front of my eyes without my glasses.
Also, I could only get my prescription filled in high-index lenses as the normal lenses would be too thick for nearly any glasses shop to order and grind. And had been that way for at least a decade by the time I opted for LASIK.
Poor control of my eye reflexes meant that even after over a year of trying I still couldn't reliably wear contacts, and was a highly stressful part of my day when I managed to get them on.
I had a family friend that went for LASIK very early on (late 2000s iirc) and had a horrible outcome losing sight in one eye, and a couple of friends in college that had amazing outcomes, so I had seen both sides. Ultimately, the LASIK operation was a very quick and pleasant operation for me, and the results were beyond my expectations. Nearly a decade later, my eyesight is still fine though I think I'm starting to see some blurring at middle distances that wasn't there a couple years ago. Did get some strong starbursts at night for a couple of years but I've either gotten used to them or they've faded.
After wearing glasses for around 20 years of my life, I love the freedom of no longer wearing them.
I always figured it was from Nuclear pearl-clutching and genuine fear about launch disasters. Especially after the various Apollo and shuttle disasters.
Though with how SpaceX has been blowing up rockets left and right, probably a good idea to not have nuclear materials launching until that's been resolved entirely.
Boca Chica beach is a mess now, I can only imagine what new Fallout installment we'd get if South Texas became irradiated from a failed launch.
> As someone who has actually built working micro payments systems
The Github repo clearly has Python and Typescript examples of both client and server (and in multiple frameworks), along with Go and Java reference implementations.
Maybe check the whole repo before calling something vaporware?
Yep. They claim all sorts of things, but there is no transparency or proof that any wastage or actual fraud was present.
It's all just ideological things that Project 2025/MAGA/Daddy Musk doesn't like. The CFPB is a perfect example. Musk wants to get into finance so he's gutting a department that only exists to protect consumers.
It's a damn shame the IRS funding is getting gutted and those billionaire 1% will be getting cuts anyways. Hard to go after those not paying when Daddy Trump and Daddy Musk cut the legs out from under the enforcement and audit folks.
One of my favorite series in the last few years. The tech side of things are believable enough (at least compared to the usual handwavy nature of sci-fi books) and now I understand why, as it seems Wells has a history in IT!
I'm struggling to not gush about this book and trying to avoid spoilers, but if you like a good sci-fi action/adventure book with a strong lean towards a journey of self discover it's really worth a read.
It also doesn't help that the bid/contract process is skewed to select the lowest bidder.
You can always forget to add some margin here or there, or fail to plan for problems that might pop up. It's easy to game the system because sunk costs make it nearly impossible to switch once you've started.
And how many would assume that the incorrect unit abbreviation would mean something else? If I said Kbps and KBps, it's an entirely different unit of measure. NM and nm are VASTLY different, and unless you are already familiar with measurements in Aviation and know it's Nautical Miles, your first instinct is gonna be to read it as the unit it's supposed to be.
The article title is talking about location data and computers, I've seen many people forget floating point precision when comparing and getting bit by tiny differences at the 10^-9 or smaller. That seems just as obvious on the outset as non-unique location designations in what the average person would assume to be a dataset that's intentionally unique and unambiguous.
I too first read it as nanometers. Perhaps it's just those with engineering/science backgrounds who have far more experience with nanometers than nautical miles?
I've never had cause to see the abbreviated form of nautical miles, but I know nanometers. Also, given purely the title I could see it being some kind of data collision due to precision errors between to locations that should be the same airport but perhaps two different sensors.
Recently unionized at my workplace and the most vocal anti-union folks were high-level/long term employees that went "Well I have mine, I can negotiate my own wins", while saying they weren't willing to pay dues just because some folks couldn't negotiate on their own.
Ignoring that half the reason they can ask for whatever they want is that they are the last standing expert on some esoteric internal thing. Of course you get treated well! Too bad the rest of us don't have 15+ yrs here and practically own this or that piece code.
The question was would you spend that on a device you spend 8+hrs in each day, which is something people often ignore.
This is a device you _live_ in. This is someone's mobility and independence you're talking about. Not a "I spend 30 minutes to an hour a day riding", or a "I commute to work on this" but instead "I use this to enjoy life".
Well that's reductive and dismissive. These are perfectly understandable mistakes or scenarios one might find themselves and a simple method to avoid/rectify them.
Find is a very powerful and useful tool, and the author gave a clear example of when and where it might be useful. They also called out how to prevent accidents with `rm`.
I taught my research group Git version control in college. It was part of a "new student/researcher onboarding" series that we put all the new grad students and undergrads through. But we were in Radio Astronomy, so there was a lot of data processing and modeling stuff that required being comfortable within a remote ssh session and the basics of Linux/bash/python. I know it was already being used in Radio Astronomy (at least in the sub-field of Pulsar Astronomy) at the time and was part of the reason I didn't get pushback when I proposed making sure our group was trained up on using it.
We switched to Git as a whole in early 2009 since it was already a better experience than SVN at the time. Could be off by a year or two, given how long ago this was and the fact that I was working with the group through the end of high school in 2007-2008.
We only added GitHub to our training later in 2011-2013 era, but we ran our own bare git repos on our department servers until then. And students/groups were responsible for setting up their own repos for their research projects (with assistance/guidance to ensure security on the server).
Last job also made use of our own internal bare repos, admittedly mirrors of our private GH projects, and our stack pulled from that mirror to ensure we always had an instance that was not dependent on an external vendor.
Current role also makes use of bare git repos for similar reasons.
I think the knowledge is there and plenty people do it, it's just not news/blog worthy anymore. It's not new or groundbreaking so it gets little attention.
I get being charged per-run, to recoup the infra cost, but what about my total runtime on my machine impacts what GH needs to spend to trigger my build?