Kinda defeats the purpose of doing it private and local.
I wouldn’t trust any claims a 3rd party service makes with regards to being private.
Kinda defeats the purpose of doing it private and local.
I wouldn’t trust any claims a 3rd party service makes with regards to being private.
It definitely feels great when I get to remove the
//hack abc due to bug in library xyz version 1.4.5, issue tracker says it’s fixed in 1.5.0. - link
// I told them I'd do this but only if they gave me time next sprint to fix it - 12-03-1997
I tried doing a dual boot to Mint awhile back, I did the mint backup at the start like it suggests, changed some things, broke it, restored from the backup thinking it was great id already made one, and broke the WHOLE pc.
I had to pull the battery on the BIOS to get it to go beyond a black screen when turning on.
It was terrible.
It seem to recall at the time recommendations about not doing dual boot, and if you wanted to dual boot, remove the main OS drive when you install Linux. Then put it back in.
I mean, on TV every character seems to be able to hack any system in a few seconds.
They clearly must have done some research by watching some NSA hackers who can hack every system.
I feel like something like https://www.storj.io/ is on the path to what we would want/need?
There might be some additional requirements for a true CDN to ensure data is closer to where it’s needed and in as many regions as needed though with the right amount of bandwidth. The data gets stored all over the place, but that doesn’t mean its optimal. But they do seem to claim it’s faster on their website…
Edit: For those not wanting to click, TLDR is they use excess storage around the world and make it accessible anywhere, and safe from failures. People with excess storage can join the network if they have enough storage/bandwidth and pass some tests. Their API is S3 compatible.
You can format the Mac and put Linux on it and get updates forever as well.
Edit: or you could when it was x86… not sure where Mx stand on that.
Those times you see an oddly specific and very weird rule and you just know there’s probably a great story around it.
No one cares if you leave a ticket open due to a bug or incomplete feature
Product sure as hell cares if you’re going to ship a bug or incomplete feature.
Never worked at company that wasn’t the case in over 15 years.
Product owns the work they ask us to do. We do their bidding.
And we certainly aren’t allowed to just change the scope of tickets at our own discretion without checking in
Apple won’t like that doomsday event lol
Give it long enough and somehow the person who decided on IPv6 will feel the same as every piece of matter we want to interact with can be networked.
I’m sure many smaller companies had their own internal Y2K moment as they scaled and became a big hit, and realized they used a wrong datatype like int instead of long or something and shit was gonna break by XYZ date if they did nothing heh.
This is my typical experience as well, too many people don’t do a code review of their own PR first.
When I was a junior, I had this coworker who did all my reviews. I was doing my absolute best and wanted to show that I was learning, so I would review all my work before submitting it and think, how would he review and respond to this code.
That just stuck with me and it’s my normal practice now.
I eventually learned that’s not as normal as I thought. I also tend to give better code reviews than others.
Edit: the other thing I do is check in with who will be reviewing my code well before I submit anything someone might think is weird and have a discussion about it before the reveiw. If it’s weird, there might be a better way unless were stuck due to technical debt or something, and doing that early vs at the end usually saves time.
So say we all
I’ve caught problems in code review and had to do this even.
Often it’s reading it and realizing there’s a complicated edge case or they missed something entirely.
Sure we can make a different ticket for that to move this along, but we’re getting product to agree first.
I don’t see him mentioning low level audio performance is a requirement. And he listed flutter as something he had considered.
Can you not process audio in the JVM?
Edit: targeting JVM he could also use the JNI and do the low level stuff in c++ if needed. I don’t know how that’d cross to iOS but it’d work on all 4 other platforms.
Edit: And he doesn’t need to target mobile either, he can just target the JVM, write it in Kotlin + Compose and if needed write native code if he needs more performance.
You can try Kotlin Compose Multiplatform.
It can target JVM (windows, Linux, Mac) and then work on iOS and Android.
Android and JVM are stable. IOS is alpha and works well. Should be beta this year.
WASM support is coming as well but is experimental.
You can do as much multiplatform as you want and do as much platform specific as you want.
Compose itself is a declarative UI framework. Your UI is code.
Edit: You do require a Windows, Linux, and Mac machine to build the executables for each desktop JVM app, as well as a Mac for an iOS app. Android you can build on any of them.
I’d greatly appreciate a “requires account” on app stores.
Looks like Lifeograph has a 3.0 release candiate which is brand new last month. Maybe they’ve have made things simpler and added a better theme?
.