1,642 karma · joined November 17, 2016
How does the editor itself work, does Xcode have components? Are you drawing them?
I've been curious to try and make GUIs for my editor of choice (vim and kakoune), so I'd love to hear your experience on the actual editor portion of your app. It visually looks nice!
Likewise, we're sitting here focused on Amazon for implementing facial recognition instead of focusing on changing laws and government "culture" to make such an act against its own citizens far from accepted. I don't like what Amazon is doing either, but attempting to stop people from advancing facial recognition seems fruitless at best. Facial recognition is here, and it's only going to get easier, better and faster.
Can we focus on finding ways to prevent/identify/etc bad actors? Because facial recognition is coming, regardless of Amazon, and bad actors aren't loyal to amazon.
Which must be worrisome for competition.
So it's all a numbers game. What's acceptable, and what we can improve on.
Ie, I assume most of the sites I visit track me for advertising purposes. This is no different than Google, it's just that with Google I expect the developers of the tracking to be Google directly. With the NewYorkTimes or w/e I don't expect them to be doing it. I expect some random 3rd party to be doing all the real tracking.
Now I know nothing about Exactis, but I'd wager (perhaps incorrectly) that their product is directly related to a product I was consuming, such as written news content or w/e.
Though tbh, I'd vastly prefer a printer that just did this, not a camera. Then I can take normal photos with my phone, maybe even preview what the drawing might look like, and then print it with the draw printer.
I'm writing my own self hosted backend for this type of thing, and I'm curious what features might be of most help for me to memorize data. Though, it's quite possibly that I'd just make a bridge to Anki, who knows.
My current thought on migration is that I'm going to write what is effectively a database (again, it's storing files locally and blah). Then, if I need to make a schema change, I'll literally copy the db code to a v2 db. The v1 will have vendored data types, so nothing outside of v1 can "break" the code. v1 will also incur no dev time because it's entirely isolated.
So "migration" basically pulls the entire database from v1 -> v2, storing it however v2 is written to.
What I don't like with this model is as you mentioned, it incurs a lot of cost of storage, bandwidth, who knows if a large migration is needed between many versions. v1 -> v2 -> v3 -> v4 and etc. Taking a TB library from v1 to disk to v2 to v3 and so forth seems.. costly. Furthermore, doing it purely in memory is optimal, but then I'm likely writing lots of code specifically tailored for in memory migration. Where as I'm hoping to basically pipe v1:read -> v2:write as the "migrations".
On the plus side though, this is mainly a development concern, and that's likely to only affect me.. I guess I'm just obsessing, and I really don't like that there doesn't feel like a clear solution here. I've not encountered this professionally.
Strangely, professionally I've had the potential to run into this, but we've always dealt with it manually. Ie, if we change how we store files on S3, it's usually a one-off fix. Here I'm trying to avoid managing my data like that, I just want to write features and have "rock solid" storage.. which means no one off scripts, and instead proven migrations.
Anyway, this is just a bunch of rambling. You can't help me with this I'm sure lol, but if you've dealt with filesystem migrations professionally I'd be really curious to see what you've done. All I've ever seen for migrations was traditional SQL migrations.
What other languages? Because the language uses "Fast as C" as part of it's tagline. Is this a false claim?
1Password has a native app, which I use on both windows and osx, and I just don't install their browser extension for autofill features.
Though, given that I avoid autofill like the plague, I could easily be misunderstanding the issue too. I'm speaking of a subject I don't use, I don't think anyone should haha.
I use an installed 1Password app, and avoid browser autofill extensions like the plague. Browser extensions don't have a good track record I believe, regardless of company. I don't blame the companies, I blame browser extensions.
I see little benefit in autofill integration, I just click the button in my task bar, click copy, and paste. LastPass has been pretty sketchy in the past too, I don't trust them. I've been quite happy with 1Password, fwiw.
That's why I felt my situation and my wife's differed. Mine was simple because there wasn't an underlying pile of complexity. Her underlying "addiction" and etc are noteworthy items in her list of things she needs to do. It's simple if you ignore the problems, but if she wants to actually implement that simple instruction she needs to figure out the little details that affect her.
So yes, it is simple if we're not talking about her situation with context and reality. Mine is simple in all contexts, in my opinion.
Smoking is a good example imo on where our opinions differ. Smoking is super far simple in my mind, because many people can't just stop smoking (or rather, lack the willpower). So they need additional data, the simple instruction was.. imo, not so simple.
I'm the type of person Soylent advertises to. I even made my own for a ~year. Keto (mostly low carb for me, not keto) has been a massive boon though. Fats just leave me so much more sated and stable. I highly recommend it if you don't like to eat or want to eat more dense meals.
For me, it is that simple. My point was that for my wife, there are a ton of other considerations she deals with. Sure, they're mainly in her head (though possibly other factors such as gut biome play a role), but large she has more details to factor in when she thinks about "will I be able to do this?". I on the other hand don't. For me, it's exactly as the author described, simple.
Yes, simple does not mean easy, but saying quitting smoking is simple to a smoker is not an honest assessment of their situation.
Most things in life are simple if you ignore reality and speak of life from a bubble.
Also, eating.. pickiness too. I don't mind leftovers, hell I don't even mind eating the same thing for a week, two, etc. She hates leftovers and always wants freshly cooked. Also rotating food types, as it can't be too similar to what she ate recently.
All combined it means that finding hearty meals (and now keto for us) are more effort for her than for someone like me. To no surprise, I have no weight to lose (I need to workout to even maintain weight), but it really frustrates her at how different our bodies are.
She considers her food habits to be an "addiction" in large part due to how different her and my reactions are to food. Her struggles are far more than mine on this front.
This is honestly what bothers me most. Firstly, I expect self driving to have massively more information at hand than humans do. I'm talking long range, 360deg sight. I expect multiple sensors to be recording at all time, analyzing. And finally, I expect a "black box" to be able to visualize all of this for cases like this.
Visualizing is something I think needs to be black-box level standardized. It's what we need to hold them accountable, I think. We're dealing with proprietary implementations - so humans should be able to review black box "footage"[1] and decide if the scenario was handled better or worse than a human.
There's going to be times where this system fails, and I'm not expecting perfection. Yet, humans in non-private positions need to be able to regulate how Uber and friends are behaving on the road.
A short sighted grainy video that looks like it was from 1990 is not cutting it. Fully unacceptable in my view.
[1]: I say footage loosely, because I imagine a lot of the scanned data is just that, data. So it needs to be rendered in a human friendly, visual manner, fully understandable by lawmakers.
1. As I'm writing, if it's in my head as a "oh, that needs to be done", I write it down. Tiny or large.
2. If it's really large, I tend to word the task as to break it up. Otherwise I'll spend a day working on that one item, which defeats the purpose of trying to give my brain dopamine/etc.
3. If at any point in code I think of those "oh, I gotta remember to fix/refactor/add that" I write it down.
It's quick because I don't need to give others context. It's short, because it's just for me and it shouldn't be too far away from my current context anyway. And finally it helps me actually take breaks, and come back getting right into it. I try to never leave without writing what I should do next.
To pair with that, I chose a todo app (Dynalist atm) that I enjoy using. It should be quick to get ideas onto paper so to say, and not bogged down with features. This is more of a notebook, than a todo.
Anyway, it's all an experiment for me. I'm on week two or so of it, and it's been great so far. Good luck if you try it :)
edit: fix stupid list formatting.
It's a business opportunity now, but as with many government laws, in the future businesses end up depending on government forcing their markets existence. So then they lobby for the government to keep the system, even if it's out dated or badly thought out. We can't stream line anything, because entrenched businesses don't want anything to change.
It makes me sad the world is this way.
Perhaps this is wrong, but I feel like another important (and possibly most common) source of procrastination is not avoidance, but rather simply getting more enjoyment (dopamine/etc) of other activities. Ie, I don't think I have to be avoiding work to procrastinate, I may simply get more dopamine from Reddit-ing and thus mentally prioritize it.
Focusing on why your work or w/e you're procrastinating from is often the wrong approach in my opinion. The competition for tasks being avoided are typically pure entertainment, all dopamine and no effort. Tasks that are "meaningful" such as work, learning, etc often can't compete with entertainment for your brains drug dependencies.
Instead of focusing on tactics to improve procrastinated tasks, I've found my life is better when I instead limit their competition. I've had serious Reddit problems in the past, where I become basically addicted to it, and so my brain keeps injecting Reddit it any time I'm compiling or w/e. If I instead break that habit through heavy limitation of the dopamine provider, I've found myself to be far more productive.
Now methods to make tasks you want to do give you more dopamine are always welcome. I love micro-todos, and found them to be pretty effective at giving me a sense of accomplishment and, I imagine, dopamine. But micro-todos will never compete with pure entertainment, so I need to cut that. Or, at the very least, cut it from my default response of when I'm having spare brain cycles (like compiling) and jumping to fill it with entertainment dopamine.
Regardless, DDG represents easily 70% of my searches.
The author's use case is very beneficial to optimize in this manner.
I've got a project where strings aren't exactly crucial, but we're storing a ton of them in memory. We store them as string and, frankly, rarely access most of them - though we do do some compares of strings on the hot path.
Using []byte sounds interesting, but troublesome at the same time. Namely the fact that byte is useless for reading characters from, as you'd eventually have to get runes from it anyway no?
Thoughts?
In general I just meant that the GUI would attempt to reduce assumptions and be as flexible as possible. Ie, I would want to be able to control multiple cursors. Control multiple highlights. etc
Bonus points if it provided various events to trigger built in IDE features like auto complete popups, debug breakpoints, file panes, etc.
Fwiw, I don't think a "generic" interface is ideal. Perhaps for basic editor tasks, but when writing a kak<->sublime (fake example), I think it's acceptable to write it specifically for sublime. Having that binding be interchangeable between sublime, atom, xi, etc seems overreaching with little to gain.
Though, to a degree a subset of general commands which all editors support would be really handy. Similar to the Language Server Protocol, if Sublime implemented the fake "Editor Server Protocol" it would allow Sublime to instantly support Kak, Vim, Nano, etc. ESP extensions for Sublime, VisualStudio/etc would provide full functionality without affecting the ESP Core.
Hmm, this is neat. Perhaps a bit lofty, I just want a nice GUI for Kakoune hah.