416 karma · joined May 8, 2018
All the brackets are currently spoken for: [] = list {} = set / dict <, > = less / greater than
I suppose you could overload <, > but I'm not sure that's much better.
Honestly, the more I've learned different languages the more I've come to the conclusion that little syntax changes like this are minor, for the most part, and what really changes the power and feel of a language are the abstractions that it allows for.
In addition to the issues above, I noticed terrible battery performance on my laptop and the fans would frequently spin up even with a single tab open.
These all have 4-5 star reviews, and otherwise seem perfectly fine. If I saw them in a store I would have purchased them without a second thought.
Ultimately I just went back and bought the first one I saw. It seems perfectly fine, I can't see any issues with it.
2. The original article you are commenting on suggests that bottled water contains more microplastics than tap water.
It looks like it is on their radar: https://twitter.com/NotionHQ/status/1093334827770699778
In the meantime, there is this workaround: https://www.notion.so/Notion-Inline-Math-9c5047a4e7c84643848...
It's not a great workaround, however, since (by the way it works) it looks like it would only work locally on the user's browser assuming they install the violentmonkey browser extension, it is rather verbose (the code block + `math:` prefix), and having to press F2 to rerender all inline math.
Clearly it doesn't have to and should not be this way. My point was that:
1. They are saying that their particular implementation did require it to be this way. 2. Almost every web app could be made to require less private data from the user, however if this is something that GDPR is going to enforce then there will end up being some subjective analysis (according to non-tech lawyers?) as to whether a particular implementation was in violation.
I have a long commute, the only thing that makes it bearable is choosing the content I listen to. The app makes a difference here - PocketCasts and Spotify have features that others don't - so I do want to use their native interfaces. The apps I use in the car have great Android Auto interfaces which simplify content selection. Using Android Auto also integrates with the other features on the phone, such as phone calls, calendar reminders, "OK Google", and maps. This essentially defines my entire driving experience at the moment.
If Tesla's interface doesn't support an app that I want to use (eg. Spotify) then I would have to resort to using the phone over Bluetooth. I wouldn't just say "oh well, I spent $50k on this car but it doesn't support PocketCasts so I guess I'll listen to something else for the next hour" every day. This makes the big touchscreen rather useless, and is going to be more dangerous than my current car because I will be fiddling with the phone.
Maybe I'll just get a big suction cup and mount my phone right on top of the touchscreen, using Android Auto on the phone itself over Bluetooth.
I guess I would end up using my phone over Bluetooth, negating much of the benefit the large touchscreen in the Tesla provides, ending up fiddling with my phone to change songs etc.
People are going to point out the privacy issues inherent in using Android, and I understand the complaint, but Google already knows my speed and location at all times anyway just by virtue of having my phone on me. I don't think Android Auto would have any interaction with the cameras or sensors, since most other cars do not have them, but perhaps others can speak to this.
Regardless, this has really diminished my interest in getting a Tesla.
While it clearly could be implemented many different ways, and I agree Dropbox should do better in this case, I think this is one of the difficulties in enforcing something like GDPR. Almost anything could be made to work in an anonymous way, so where do you draw the line? When signing up for Facebook or an email account, for example, there is no reason they need my phone number. Sure, they say it is for password reset purposes, but there are other solutions for this, or I can simply agree not to be able to reset the password for that account... etc.
This was the sole reason I checked it out, however I have grown to appreciate many of their other features. Their collaboration functionality is quite unique, and the generally smooth way you can add structured information (eg. "todos" with assigned users and due dates) is great.
That being said, it often feels "half-baked" still compared to other solutions. The Paper file organization interface feels like it is just bolted on top of Dropbox's existing interface, and sometimes their formatting is too restrictive (eg. you can't change text alignment). The issue raised in this post is yet another example of the product being half-baked.
If someone could make this device and run it cost effectively, what incentive do they have to sell it? Last I checked, the only place to make money on crypto was certain areas in China with very low electricity costs.
For me, Julia completely addresses the 2 language problem. In practice I think it now simply needs a stronger ecosystem, better static analysis, and bug fixes, but I am very happy with the language design.
I don't think anyone should have children because it helps them come to terms with their own mortality.