This is a wonderful trip down memory lane <3
943 karma · joined February 20, 2007
This is a wonderful trip down memory lane <3
I’ve found using conda, in dev, to provide system libraries and poetry (+ a build.py for our C extensions) to be a really comfortable experience.
In CI we use cibuildwheel to produce “statically-linked” wheel files. They’re not really statically linked, but they behave as though they are by bundling all dependent libraries into the wheel and doing some RPATH “magic” to look those kind up during runtime.
I’d like to reduce the delta between dev and CI at some point, but it is stable rn so I’m inclined not to futz with it.
My limited experience: my then-employer opted not to acquire a company after doing due diligence. Ultimately we decided that the price of acquisition (both paid out, and also incurred in internal time) was below the cost of building a comparable product ourselves.
As the dev who did the tech portion of the due diligence I was now “tainted” by my knowledge of their system. As a result I could not work directly on the effort to build our own comparable solution.
The history is basically:
- v1: IRC API to process scoped servers (Python backend, haxe front end)
- kept API as we migrated backed to go (via a terrible course through nodejs); this version allowed all participants to be in a room together (ie cross process servers).
- once most of background was on go we migrated the front end (can’t remember to what)
- backend then got revved a lot (a specialized team was convened to work on chat infrastructure full time)
I left in 2017, no idea what has happened since.
I guess my main schtick with the Axios piece is that it lacks any form of nuance; starting percentage increases as uniformly good.
Clearly this piece is light on meaningful details. One example is how the increase includes areas that are completely unsafe to ride — for example adding lanes that are essentially storm drain run offs which are generally unfinished - so you have to bike in the road.
Our local news has a great example of a lane with an electricity pole right in the middle of it… :facepalm:
https://www.kxan.com/news/local/austin/austin-cyclists-flag-...
Stack traces are presented in a gorgeous fashion, log.debug lines have lots of great meta data with them. I almost always start new projects with those as my first imports.
My answer to your question is: B2C consumer internet -> Cancer research.
Heap using AWS just means they've not yet reached a point on that trajectory where the capital investment moves the needle enough to warrant it. That could be for any number of reasons.
* For the first 9 months folks would often say: "I missed you at my such-and-such event last month", and I would reply: "email me next time". Perhaps if I had quit loudly I'd have felt less FOMO-y and been invited to more events.
* Births / Deaths / Marriages; I'm completely out of the loop, which is almost always a worse off situation. I've come to learn that I want to know sooner rather than later when folks have died because going through grief a week or two after other folks absolutely sucks. I wonder if I quit loudly folks would reach out more proactively in these situations?
* Generally feeling connected: a "personal talent" of mine is a relatively strong ability to remember what I read about folks on their FB timelines. Without that I feel pretty disconnected; and there are a lot of folks I "miss" as a result. Would this have been different if I quit in the open? Would folks have said: "oh you can follow my photo stream and see what I'm up to?"
That final example, when coupled with deaths, is particularly acute. You're left wondering whether you could have helped prevent self harm, etc.
[1] https://twitter.com/ossareh/status/1133957584153694214
[2] I mean this jovially, apologies to anyone that struggles with a more manifest addiction if this phrasing comes across as trite.
I work with motors that are accurate up to 5nm imaging things far smaller than 1nm, so it’s pretty mind blowing to hear that folks are actually (well, aiming to) operating on tissue at this level of accuracy.
* no indication on the PR page that actions are down
* no way to run the actions once actions comes back
My kingdom for a "rerun actions" button...
I’ve heard this a lot of late, but it’s not clear to me why. Would you be willing to expand on your assertion?
Personally, I’ve written a fair chunk of typescript and asyncio based Python over the year for a project and in general I think Python has done an excellent job of their implementation.
Some things are annoying; for example I’ve a consistent case, which I haven’t pared down to better understand, where by exceptions in a coro are never visible. Not to be confused with the classic case of being notified of the exception when your process shuts down.
OTOH some things are really amazing, for example PYTHONASYNCIODEBUG=1. More so the ability to wrap non async, typically blocking, code in an Executor and it “magically” (via thread pools) work in the event loop has also been a boon for the type of work I’m engaged in.
Waaaaay back, I was really hurt by twisted and to a lesser extent tornado. But the async stuff shipped in 3.9x seems completely comparable to JavaScript imho.
So I bought a beefier NUC (Ghost Canyon) and run ProxMox on it. I setup a NFS server in an LXC container, and then a typical VM for development[1]. In all it took me a couple of weekends to really get things dialed in nicely.
ProxMox is great, I really love that I can provision and throw away instances quickly! It makes for less variance in trying to establish what made thing X work suddenly.
[1]: I need kernel modules and the guest to have access to USB for my dev
In my case my nuc and my “terminal” are connected via 1Gbps Ethernet. Vim in tmux was terrible; line by line scrolling was very jittery. Witching off font ligatures meant the GPU was able to handle rendering and now everything feels really smooth with multiple vim panes open.
Prior to moving back to terminal based editing I was very much in the same spot as the OP, using VSCode - I didn’t notice any form of latency with that setup.
The lease would be dropped and renegotiated every few hours, we could notice it because our SSH tunnels would get torn down.
What was annoying was that the business plan had a static IP associated with it, presumably managed by their DHCP setup.
It took weeks to convince Comcast the issue wasn’t in our building, and moments for them to fix once they “got it”.
--
What to Submit
On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.
Off-Topic: Most stories about politics, or crime, or sports, unless they're evidence of some interesting new phenomenon. Videos of pratfalls or disasters, or cute animal pictures. If they'd cover it on TV news, it's probably off-topic.
I’ve a few friends who are personal trainers, they all complain about the “zoom centric” solution where by as a client you dial in to a zoom call, and have to move a phone, iPad, whatever, around a bunch so the PT can see you.
My mates have suggested that what they really want is to be able to select from a range of views while a client performs some maneuver.
While this doesn’t solve the upstart cost (multiple cameras, bandwidth, etc), it’s cool that it does solve the “hard part” of working out how to stream to some common end point that allows the viewer (the PT) to select the best view.
If you’re earning in a country with a treaty, say the UK, you pay the local tax and any difference is paid to the US if your local tax is less than what you’d pay the fed+state if applicable.
I’d love this on a touch screen picture frame in my house were folks could play with it! I’d easily pay $150 for that.