CoQ10 is the primary antioxidant the human cell provides to protect and support mitochondria. It helps generate ATP within the mitochondria, the main energy driver we have.
CoQ10 is ubiquitous and produce within the body, however after the age of 20 levels start to drop, so it makes sense to consider supplements to top levels up if you're north of 30.
I love the stuff myself. I went from a tired feeling 45 year old with brain fog, to having a lot more energy and a mind keen to engage all day with whatever I have going on at work
You should watch this excellent video by Dr Stanfield (actually, entire channel is excellent) in which he goes into Cochrane Medical Reviews among other research channels to dig into the science around all this stuff.
Dr Stanfield recommends sulforaphane over C0Q10 and the science/medical evidence he presents is compelling; he has a few videos specifically on sulforaphane as well.
I would highly recommend anyone that is doubtful of vitamins and suppliments, particularly relating to aging/longevity - really give this YouTube channel a thorough review. It's hard to discount Cochrane Reviewed[0] backed data.
Emacs is definitely ugly and antiquated. It has terrible curb appeal. But unlike any "pretty" software I've ever used, if one sticks with Emacs long enough, sweating bullets to learn its odd ways of doing things and customizing it, there comes a point where you suddenly realize it's reading your mind. After that, it's impossible to imagine getting work done on computers without Emacs.
Yes, a common reaction, until newbies (like myself) find configurations like Doom Emacs and Spacemacs and come to realize the opposite. For myself it's only missing a slightly better "rending experience" like VSCode.
I love Spacemacs but due to varying configurations per build on different OS' Emacs either doesnt work at all OOTB with Spacemacs for me, or it works just enough to show up broken. Without cross-platform consistency I'm better off using Neovim + Spacevim which sometimes fails on me due to fonts, but its less broken.
I tried both of them and just gave up. Emacs for me has nothing on a modern IDE and a light weight vim config for file editing. When it comes to reading email, browsers are far better option.
Just some feedback, but I would consider doing a free tier for open source projects which would get your the coverage and in turn the adoption you need. You need to win developers over who in turn influence tool procurements.
A typical cereal serving is 45g, which is a very small volume, the box I have in front of me tight now tells me it’s 250kcal. It’s super easy to eat muuuuch more than that because carbs are so satisfying they’re downright addictive.
Two bowls of cereals can fly very quickly into one’s belly, pour in some milk and the tally easily crosses the 1000kcal mark.
I have found most Idea performance issues are either, configured Java heap space, or indexing of project files that could be ignored.
The default memory settings are generally pretty conservative, some larger projects run into issues immediately.
If your system has plenty of ram to spare, I would recommend just giving it a few gig and seeing if things improve.
I don’t notice slowness on it personally. Maybe you are noticing the initial indexing it does. That doesn’t happen often with GoLand.
Make sure you enable Golang modules in the settings also.
Anyways just mentioning some stuff off the top of my head I enjoy:
Debugging is a great experience.
Can find a plugin for most anything, I use the Kubernetes one for syntax completion and documentation. (alt-q I think)
Also you can create .rest files and compose http requests and trigger them right in the files, which I thought was cool.
The documentation pop up by hitting alt-q in general is pretty cool. Don’t have to run over to godoc.
Then most things you’d expect from an advanced ide. Multi line editing... jump to definitions and implementations... Project wide code search and replacement
I'm not sure about Go's specific characteristics, but for PyCharm I love full project semanticly analyzed code navigation and remote step-through debugging. I use visual studio code for most JS stuff, but it's awful for wrangling many files simultaneously and learning a big codebase. Webstorm allows me to search for function calls and other things in the entire codebase much faster. I prefer VSCode's git UI and use both apps.
I can compare it with VSCode. Goland is much better at working with multiple Go Versions, which is a big thing in my daily work. Other things that it does better than VS Code are auto-generating unit tests, refactoring function signatures, better package management support, easier to set-up different build/debug profiles ...
Probably Sublime text. It's just too fast and I can't switch to anything else. I open heavier ones like Eclipse, VS Code etc. only when I need to refactor.
Here was a 3rd party analysis from 2015, showing a reduction in latency when editing XML files in IntelliJ IDEA from ~70ms with large jitter to 1.7ms with small jitter: https://pavelfatin.com/typing-with-pleasure/#summary
I wonder if it's turned on by default today, 5 years later.
at least for JS, the refactoring tools save a lot of headache. write code before deciding on variable or function names and then one click to refactor everywhere in the codebase.
Can anyone explain to me why I should be concerned about vs code telemetry? I have zero personal information in the IDE and all the code I work on is already in the public domain with an open source license, so why should I care?
How right or wrong it is to collect information about people and what they do is not entirely determined by how much personal information there is to get.
Just like how right or wrong it is to break into someones house is not entirely determined by what they take, or how much personal information you have in your house.
But yes, if you don't have anything valuable in your house, maybe you don't need to be concerned about people breaking in, but that doesn't make it more right.
Such analogies really depend on what the telemetry contains (granted, I don't know in this case). I.e. you describe it as stealing from inside the house. Say, VSCode figuring out your email adress and reporting it. But it might as well actually be pretty anonymous non-personal data i.e. more like looking at the outside of a house and taking note of that. Say, VSCode reporting the theme you use, and just that.
> Say, VSCode reporting the theme you use, and just that.
Wouldn't that be like looking through the windows to see what clothes they wear or at what time they go to bed or who they sit at the table with?
Just because you are outside of someone's home it doesn't mean you can't invade on their privacy.
Why does an editor need to do telemetry to begin with? Mind your own business. If you don't want to give me something for free, don't. Don't make something free and then feel like you have the right to spy on me. Charge me for using it.
Wouldn't that be like looking through the windows to see what clothes they wear or at what time they go to bed or who they sit at the table with?
Hehe with 'theme' I was actually just thinking about the color of the outer walls, should have made that clear. Even then: passing by a house and peeking through a window once is usually legal and as far as I know doesn't require consent (at least not in my country). Stopping in front of the window and staring inside for hours, not so much. Nor is passing by at the exact same time everyday and peeking inside.
Why does an editor need to do telemetry to begin with? Mind your own business
I'm not advocating in any direction here, be it pro or against telemetry. My point merely is that before making analogies, you'd better first check what telemetry exactly is being collected otherwise your analogy might be completely off.
Telemetry is commonly used for statistics on how a product is used, to learn for example if the user interface is counter intuitive or obnoxious with a much better sample size than their own team.
I also note that we still don’t have a clue in this discussion what the telemetry even includes despite tools and probably even documentation detailing this already existing. But I guess it’s more fun to debate this from a philosophical standpoint than the product in question.
From everything I’ve read, MS (and other telemetry-happy developers like JetBrains) see telemetry as a way to gather statistics about UI interaction patterns and popularity of this or that component, so that they can prioritise development towards the most popular features and problems. It’s a bit like our good old “Popularity Contest” package in Linux, but applied to UI elements and behaviours. It’s the sort of thing that resulted in a massive Paste button on the first Office ribbon, because telemetry said Paste was the most used feature.
Sometimes I wonder if I should turn all telemetry on, so that they’d have a datapoint that actually matches my workflow rather than Joe Schmoe’s. It’s a bit invasive though, and culturally speaking is a horrible model (“I can’t change things unless you let me watch what you do all the time”).
Obviously if you care about privacy you should keep telemetry off, but to be honest, if you don’t trust Microsoft to respect common decency about private code, you just shouldn’t use a tool they built in the first place. I use JetBrains tools and trust them enough to leave telemetry on (“voting” for my preferred features, effectively). If you do any politically-sensitive work, though, you should absolutely stay the hell away - because then it doesn’t matter what they do with it today, but what they could do if they wanted (i.e. under pressure from authorities).
Obviously if you care about privacy you should keep telemetry off, but to be honest, if you don’t trust Microsoft to respect common decency about private code, you just shouldn’t use a tool they built in the first place.
Isn't that the point of today's discussion: you can use the privacy-respecting alternative instead?
It's still effectively developed by MS, so it might be doing something funky outside of "regular" telemetry and you wouldn't know unless you fully audit the entirety of the codebase.
Sure, but now we're comparing an open source product you can build yourself that might be doing something shady but where we have no evidence of that, against a product derived from the open source version that is openly adding privacy-eroding functionality, and with a corresponding privacy policy that is ambiguous at best about how far it will go.
I also note that we still don’t have a clue in this discussion what the telemetry even includes despite tools and probably even documentation detailing this already existing.
Unless there are clear statements and guarantees that nothing will change in future updates without the user's express consent, the statements themselves aren't worth much anyway in this kind of discussion.
Microsoft's privacy policies are notoriously opaque, to the point where you'll have trouble verifying that, for example, they aren't granting themselves the right to upload your source code. This observation almost invariably attracts downvotes, but anyone who thinks I'm exaggerating can easily refute the point by citing the places in Microsoft's documentation that say otherwise and guarantee not to change that in the future.
My point is that it's not just what information is being taken that matters.
Even if you don't take anything it's still wrong to do things inside someone's computer or home without permission.
Maybe VS Code asks for permission properly and gives the user sufficient control and has good defaults,
I don't know, but it's difficult to do that properly because people don't understand computers as well as they understand the rest of life.
By "computers" I really meant "the complexity in the software that computers run".
Computers do very complex things and most of those things can't be directly seen.
So if you want to tell someone about what some software is doing, it's not always easy.
Because some other people might be working with code that is not in the public domain, or code whose mere existence should be kept hidden (so even relatively innocent things like project, file or branch names should be kept secret)?
I personally prefer tools that don't spy on me. In 99% of cases I probably won't care, but I don't want to take the chance of the 1% where a telemetry request would send out something I'd rather keep private which is why I want tools that are private by design.
My screwdriver doesn't spy on me and report what kinds of screws I use it with, the hammer doesn't either, I want my text editor to behave in the same safe and predictable manner.
As an application developer it's quite frustrating to be left completely in the dark about how people actually use my applications. All I can do is guess. Those guesses are most probably incorrect and the app won't be as good as it could.
Just a simple button click heat map would be very useful info to have. But then sending click heat map is the same thing as stealing credit card info in the minds of many ...
> to be left completely in the dark about how people actually use my applications
You don't have to be left in the dark. You can ask people for feedback (yes that used to be a thing) or run user testing sessions (yes that used to be a thing too but seemingly not anymore when we look at the quality of modern software).
> the app won't be as good as it could
I have yet to see any evidence that telemetry improves software quality enough to warrant the privacy trade-off. If there is a correlation it seems to be opposed; telemetry started becoming popular in the last decade, and the last decade is also the time around which software started declining in quality or usability (see Windows 8+, certain changes to macOS and iOS, bloated or user-hostile websites, etc).
> Just a simple button click heat map would be very useful info to have.
That heatmap thing will also at least leak my IP address, software version and a persistent UID that will allow the backend server (whether self-hosted, or powered by a nasty ad-tech company like Google analytics) to keep a log of my IP changes and usage patterns.
> You can ask people for feedback (yes that is still a thing)
That's not very reliable. It's quite common behavior that people give feedback only when they are not happy so you can get feedback like "this is horrible" although it still works nicely for the silent 99%.
> or run user testing sessions (yes that used to be a thing too but seemingly not anymore when we look at the quality of modern software).
Difficult to do for projects with $0 budget. I'm also interested in the long term (experienced) users behavior which is not possible with such testing sessions.
> That heatmap thing will also at least leak my IP address, software version and a persistent UID that will allow the backend server (whether self-hosted, or powered by a nasty ad-tech company like Google analytics) to keep a log of my IP changes and usage patterns.
* IP address - I don't care about your IP, that does not give me any useful info
* software version - sure, I'd like to know which version you run. Is that really privacy violation though?
* persistent UID - that's a matter of discussion, for me what's important is behavior within one session, connecting several sessions is not so important and I could do without it, so no persistent UID
Each of these items could be a matter of discussion - it would be nice to move the discussion from "all telemetry is literally evil" to "what's acceptable to collect?".
I disagree with feedback not being reliable. I think that detailed feedback from someone being not happy give you more details than a heatmap for example. I also think that feedback from a user who takes the time to actually leave feedback (and so is more invested in the product, and likely to give you repeat business) might be more valuable than one-off users.
> I'm also interested in the long term (experienced) users behavior which is not possible with such testing sessions.
Is it not possible to reach out to those users and invite them to such a session in exchange of $$$?
> I don't care about your IP, that does not give me any useful info
True but some malicious third-parties might care, whether it's the analytics service itself (Google Analytics comes to mind) or even a law enforcement request to capture/access such data. You are basically creating a potential liability for the user; some people might not want the software to phone home for certain reasons and I think the default should always be safe so telemetry is "off" by default.
There's also the issue that telemetry is typically opaque and the user has no visibility or control over what is sent, so out of an abundance of caution they opt out. I think a good improvement would be to queue all the telemetry data locally, and then periodically ask the user to review, edit/redact & send it if they want to. Apple has done it relatively well there where if an app crashes they allow you to review the report before sending it, and I actually send these the majority of the time (unless it's a process dealing with sensitive data) despite having OS-level telemetry disabled.
> I think that detailed feedback from someone being not happy give you more details than a heatmap for example.
Detailed feedback is definitely nice, but it's quite rare & not sufficient. It's again one person's view, people also often can't articulate what's wrong. Usage patterns across many users may reveal what's wrong ...
> that feedback from a user who takes the time to actually leave feedback might be more valuable than one-off users.
Both are valuable - one-off users might be people who got confused enough to be discouraged from using the product. That's extremely useful info.
> Is it not possible to reach out to those users and invite them to such a session in exchange of $$$?
Impossible for projects with $0 budget.
It's also very unreliable since people working on artificial test data have very different behavior than when they are working on their production data.
> ... people also often can't articulate what's wrong.
Then you’re not asking the right questions to get useful answers. People often can’t articulate anything well unless they’ve had the practice of doing so. I regularly interact in professional and private settings with people who regularly cannot articulate their thoughts, feelings, or ideas on things. I get them to do so by asking the right questions, digging deeper into what responses they give, and putting it all together.
The questions you ask determine the understanding and clarity you receive.
This gets brought up all the time and what I can't figure out is why user interfaces have gotten worse over the last 10 years, even as developers have gathered unprecedented amounts of information from telemetry. Is the most common feedback developers get from telemetry "good, but needs more whitespace"?
Telemetry tells your ISP and national military your usage patterns, too. When, where, and how often you use the tools is itself private.
Imagine a private journal that reported to the government every time you wrote in it, and what city you were in when you did so.
Furthermore, VS Code is specialized software. Using it in certain places allows a specific user to be tracked and identified out of millions of more "normal" traffic patterns, as developers are still a tiny minority in society.
Because maybe developers in your bank or hospital are using IDEs with nasty telemetry that might expose data on you? Maybe they are editing a branch called "workaround-for-mr-cachestash-bankrupcy-account-bug"?
Indeed. And since they are very open as to what they collect, feel free to point out anything disturbing.
As for the publicly posted results, it seems to me like they try to understand who uses their products and how. That's not worse than basic website analytics, and that's data they certainly need in order to prioritise their development.
But I may be missing your point. Can you point to a specific datapoint in those documents that you object to, and explain why?
When they post full csv files with all kinds of command line arguments including typos, who's to know your "dotnet run fix-aspycts-bankrupcy-account" command, where you forgot the first "run" argument, won't end up in a csv some day?
I can't believe I have to argue about how bad it is to have CLI tools send their arguments as telemetry. Even half-arsed lately introduced attempts at redaction doesn't change the fact that the entire mindset of the developers are poison.
And how exactly do you think they would look at all the source code in the world? Humans are too expensive.
So probably AI. How would AI tell the difference between valuable banking software full of bugs and your side project full of bugs?
Also from there, why would you include a customer's personal information in your code, or even have it on your own machine?
Really, the chances of vscode's telemetry leaking personal user information is super extra low, unless you're obviously doing something wrong with your code.
Ah, and finally, if you're using github, they have a much more efficient way of getting your code anyway.
It's interesting, if we look at the size of webpages in everyday browsing, which can go from tens of megabytes to a few kilobytes when blocking tracking/analytics scripts.
I wonder what would be the back of the napkin calculations for network traffic and energy savings (local and server side) of regulating tracking and telemetry?
Is there an environmental case to be made against modern web practices on tracking and telemetry?
I've really come to dislike Google over the past decade or so, but I do like that their Speedtests, Lighthouse etc don't hide this fact from you.
Pretty much all sites I've been asked to look at were getting low scores because of Google Tag Manager, Adsense and the like. It has a very measurable impact, and yeah, removing it speeds up the page.
The environmental case will probably not fly for regulation, but it just might in public shaming of large companies. "Hey, $company, your usage of $trackingTech uses as much power per year as an average family of four. Is that really in line with your green approach?"
This is exactly one of the reasoning pillars i'm using in arguments about the "innocuous" nature of telemetry and tracking.
Any new product that collects telemetry/does tracking requires storage that is bought and connected to a power source with high availability given it performs I/O all the time.
>>I have zero personal information in the IDE and all the code I work on is already in the public domain with an open source license, so why should I care?
Off the top of my head: API tokens and other credentials that live right in the file while you develop and debug.
Those are quite sensitive. To put more wight on the issue[0]
Since when does the telemetry even send out any contents of any files?
Since pretty much forever? At the very least, many programs with built-in telemetry have included things like memory dumps of key areas at the time of a crash, which could include data the user was working on at the time.
More seriously, I invite you to read Microsoft's extensive privacy policies and try to satisfy yourself that they don't grant themselves the right to upload your code. They are sufficiently nebulous and ambiguous that they could probably be interpreted that way.
>> Since when does the telemetry even send out any contents of any files?
To me it's not evident otherwise until i'm capable of observing bare data itself. Not obfuscated, not in some proprietary format to secure it in-transport but the raw stuff.
MS states there's no reliable way to let people see the data being collected (even under GDPR) as there's no sing-in experience provided.[0]
While a part of the statement is true, most of privacy conscious VSC users aware that every installation of the product has a unique `machineId` property. Can be located at Output -> Log (Shared).
The [0] provides some elaboration:
"We do send information that helps us approximate a single user for diagnostic purposes (this is based on a hash of the network adapter NIC) but this is not guaranteed to be unique. For example, virtual machines (VMs) often rotate NIC IDs or allocate from a pool. This technique is sufficient to help us when working through problems, but it is not reliable enough for us to 'provide your data'."
So, given the premise the user can be identified by a NIC plus a machineId (which looks to be an UUID) — it's easy to get access to collected data. As soon as ability to verify no really critical data is collected, i'll switch back from VSCodium.
I choose to trust MS are using the telemetry for improving VS Code, which I genuinely love, and accept the "risk" that MS somehow abuses the telemetry. I see this risk way lower than e.g. Google or Facebook abusing data they can collect about me.
You're all going to think I am a crazy, but I instead elected to tape my mouth closed with 3m tape right when I go to bed. This to me is superior and should be your first port. Not only did it fix my apnoea and huge lack of energy during the day, but also my chronic sinus issues that had plagued me for years. Its also a lot cheaper, much easier to use / travel with and gets me into a good habit of nose breathing during the day. A CPAP machine is still reinforcing the poor habit that may well have contributed to your sleep abnormalities in the first place. Mouth Breathing. It costs $2 for a roll of 3m tape, so it's not like it costs a lot if its really not working for you.
Mouth breathing is horrendous for your health and well being. There is a good reason why it was ostracized in the past ("mouth breather" was an insult). It was a clear sign of poor health in an individual.
It's one of the best unknown health hacks out there.
A CPAP does not require mouth breathing. Nasal pillows require you to breathe through your nose. If necessary they shut your mouth with a chin strap. A piece of 3m tape sounds dangerous for someone if the problem is nasal obstruction or rhinitis rather than their mouth dangling open. They might not be able to gasp for breath and experience an even worse apnea.
I read Sleep by Nick Littlehales and he mentions that taping your mouth closed is one technique you can use - I think I recall he says some British athletes (cyclists?) use it - but doesn't recommend it for anyone with a medical problem.
I would go even further: try to train yourself to use your nose all the time, specially around sleeping. Think of keeping your mouth closed before sleeping and if you wake up noticeably having breathed through your mouth take a mental note to change. It worked for me (no tape required).
(Whatever works for anyone of course. If other methods still leave bad sleep, by all means use a machine!)
> Mouth breathing is horrendous for your health and well being.
I completely agree with this, but using an APAP and breathing through one's mouth are unrelated. There are full-face masks that let one breath through the mouth, but the mask that came included with my machine was a nose pillow. Since air is continually being pushed through my nose, breathing through the mouth is very hard to do.
You don't need to spend $90 on some patented thing. Use simple 3M Micropore Surgical Tape 2.5cm x 9.14m, its what every one else uses for mouth taping and its exactly what a lot of dentists will suggest is used, although a few more folks are using SomniFix Sleep Strips as well. Tape works absolutely fine though, and its the consensus go to by most users.
Good point, you know if this works for you, that is all that matters at the end of the day.
The tape stays on very well. You want Micropore Surgical Tape - 2.5cm x 9.14m. Also it helps if you don't have a beard. This was the only down side for me, but I will take the better sleep / improved health over a beard.
No, not at all. I heard it first from a dentist and its quite common, well more common than would be expected. Its also perfectly safe, if your nose becomes congested you rip it off in your sleep.
It fixed my apnoea and chronic sinus issues. Seems I was constantly developing nasal polyps from mouth breathing all night.
Dr. Li does surgery for sleep apnea. I was referred to him once for evaluation for a surgical procedure only he does (EASE/TPD) and which I was told that the referring doctor had seen a lot of effectiveness in improving sleep apnea in their patients. He seemed like he knew his stuff and was very up-front about being conservative about making predictions in my case.
I would be a little sceptical of someone whose whole career is based on nasal surgery to fix apnea playing down a simple non evasive alternative. He lists zero studies to back his premise of it being dangerous.
> You're all going to think I am a crazy, but I instead elected to tape my mouth closed with 3m tape.
It does sound a little crazy, but only because I'm surprised there's not a more comfortable solution. Tape on my mouth would prevent me from falling asleep.
Is there not some sort of mouthguard that blocks airflow, and thereby achieves the same result in a more comfortable, less sticky situation?
Its a little weird the first night, but after 1-2 minutes its strangeness dispersers. In a way its no different to holding your nose. You can get mouthguards, but they don't work very well. You end up drooling all over the pillow and half gasping for air and spitting it out. All you need is a nice single strip of 3m tape.
I found it helpful to work on nose breath power. I needed to for boxing as I was mouth breathing. So on my jogs I started to nose breath took some time to get the throughput I needed but sleep improved and general breathing feels much improved.
Can you provide some articles/videos for techniques? I've been a mouth breather my whole life and wonder if I could improve my running performance by switching technique.
These 2 exercises worked for me. I did this 5 days a week (around 15-30 mins) and it took approx 4 weeks to get to a predominantly nose breathing situation.
1. Jog slowly at a pace that is comfortable while breathing through your nose.
2. Speed up pace until you feel like you will need to breathe through your mouth stay there for 10-20 seconds.
3. Slow your pace back down to where it's comfortable.
4. Adjust your pace up and down between these zones in intervals.
5. Over time increase pace and interval length.
- It's ok to take some mouth breaths as you continue practicing. The goal is to increase % of breathes via nose.
- When you get the hang of that try it while jumping a rope.
Seated breathing exercise, do with shirt off to observe abdominal and chest region while practicing:
1. Sit comfortable, good upright posture.
2. Breathe in fully and hold for 2 seconds.
3. Sip in as much more breathe you can and hold 2 seconds.
4. Sip in the final amount you can and hold for 2-3 seconds.
5. Exhale out fully and hold for 2 seconds.
6. Exhale out tiny bit more and hold for 2 seconds.
7. Exhale out tiny bit more and hold for 2-3 seconds.
8. Repeat from step 2.
- I found this really good to do in a park or in nature.
These two where my main exercises on top of using that in boxing.
- In a fairly short amount of time I was able to get a full lung breathe through the nose easily.
Tape your mouth at night! On your easy runs, breath solely through your nose.
For the record, I am an ultra runner. Nose breathing is hugely beneficial for endurance athletes. I have seen my pace come up while heart rate / perceived effort remains the same.
I did the last years entire Montane Spine Challenger just breathing through my nose (108 mile race).
CoQ10 is the primary antioxidant the human cell provides to protect and support mitochondria. It helps generate ATP within the mitochondria, the main energy driver we have.
CoQ10 is ubiquitous and produce within the body, however after the age of 20 levels start to drop, so it makes sense to consider supplements to top levels up if you're north of 30.
I love the stuff myself. I went from a tired feeling 45 year old with brain fog, to having a lot more energy and a mind keen to engage all day with whatever I have going on at work
https://examine.com/supplements/coenzyme-q10/#effect-matrix