What should I do?
645 karma · joined December 16, 2018
What should I do?
People here are nitpicking over the definition of the Turing test. What actually matters here is that, if not already now, but certainly in 1-5 years neural nets will most certainly be good as the 99th percentile artist.
Does that mean AGI is here? Probably not. But we are missing the forest for the trees.
Seems like some of the Pix => cash features are different.
Rust seems harder but it allows for compiler guided development. So there's a bit of an upfront learning cost but the maintenance cost is lower. If you change something in an enum variant, the compiler will basically tell you what to change everywhere in your codebase.
Specifically, Rust code has less assumptions, with lifetimes, mut, etc., Rust code is much easier to read. If I read a function, I need less awareness of other parts of the codebase because so much of the information is just there.
Counter-point: This is clearly not perfectly true, considering that I would still recommend Typescript over Rust for web dev.
More elitist take:
Rust is not hard. If you can pass a college algorithms class (i.e you can understand BFS/DFS/DP/Network Flow), you can understand Rust.
If your developers cannot write Rust code, you will probably pay the price in whatever language they write.
Counter point: This is clearly not 100% true since I would not say the same thing about Haskell even though arguably I could.
I used to think ML models could be good for scraping too, but this seems better.
I think this + a network request interception tool (to get data that is embedded into HTML) could be the future.
The purpose of life is not to know JQ. I just want to process the JSON so I can move on and do whatever is actually important. Ideally, I'd just be able to tell GPT-codex to do what I want to do to the JSON in English.
We're not there yet, but in the meantime if there's another tool that allows me to know less in exchange for doing more, I'll gladly use it.
What is Vale's thesis?
It reminds me of ML where the bottleneck is often the bandwith between the GPUs.
And as expected working side by side / living in the same house dramatically increased productivity. I couldn't imagine a remote employee being as motivated.
TL;DR -- startups need a certain workaholic mentality / intensity. In-person work can provide this.
In defense of remote: We didn't have a commute, which saved us at least 1.5 hours a day.
I also wonder if there is a frecency file jumper, like z.
Very interesting that the author managed to hit a pathological case in rustc.
Most languages don't seem to do a lot for run-time debugging. Being able to `gdb` and step-through on a local binary is a far-cry from detailed metrics / visualizations. We end up resorting to stuff like Honeycomb, but I'm waiting for the days of a programming language built for the ground-up for runtime debugging.
Anyways, this feels like an important step in the right direction and I'm excited to try this out
For example: Here, there was a vote. Now what? Will Blender setup a wallet that can accept ETH? Will the DAO then vote on a transaction that sends money from the DAO to Blender's ETH wallet??
- edit my files in Google Docs (seamless sync)
- play games w/o ever downloading them
- do design in Figma
- swipe on Tinder w/o ever having to install or uninstall it
- browse code on GitHub
I want as much stuff as possible to be on the web. I dislike having to install applications locally.
On a less self-centered level, the web helps small businesses succeed. Do startups have the time to develop 3 different applications? I don't think so. The power of the web allows people who don't need to be developing native apps to avoid duplicating their work.
The web seems extremely important to small business innovation.
As for "large" / "bloated" sites. Features like new CSS properties seem unlikely to add more bloat or degrade accessibility.
If we left the web as hypermedia / documents only we would have killed its potential (figma / repl.it / so many others wouldn't have existed).
A concrete hypothesis might be: Less people would have left Base Camp if they were not remote.
I can write statically typed code that easily shapes & reshapes objects & code that fits functional or object oriented programming styles.
It's a statically typed language that feels dynamic.
Now, if I were to get a version of TS without all of JS's crutches that would be amazing.
Deno is pretty close, but it lacks on performance & is bounded in potential by JS (in some aspects).
- A simplified/sounder natively integrated version of Typescript's type system - Javascript's easy notation for manipulating objects - None of Javascript's other baggage/cruft - Something akin to go routines
Basically, something with the performance of Go/Java (so there would be no need to rewrite your code once it starts serving millions of people) but the elegance of Typescript.
Not sure if this is similar to your vision of a "next Python" but it feels somewhat similar.
Basically I think right now:
C -> Zig
C++ -> Rust
Java -?-> Go
Python/Javascript --> ???
With native typing we could get a language as fast as Java/Go but with the cleanliness of Typescript.
To the author: I would rather just see the actual popup instead of inflammatory language.
To me, Parler has equivalencies
- AWS linked to calls for violence that were made on Parler
- The platform was actively suppressing non-conservative viewpoints
I would recommend looking at r/ParlerWatch on Reddit
This is not a difficult scenario.
Many people are saying SQL isn't that hard to learn but as someone who is new to SQL, I disagree.
It takes a max of 15 minutes to understand basic JavaScript/Go/Python primitives and write a program. SQL on the other hand seems much more complex. I might as well be reading Haskell or Lisp. At least those languages are consistent.
SQL does not feel like a language where I can learn a few primitives really quickly and compose them together.
The legal document also clearly indicates that Julia is collecting a very small amount of info, so there's no trickery either.
User's need to consider the developer perspective. Julia is a product with millions of hours sunk into it. It needs to sustain itself, since it's open source.
I doubt the telemetry is being used for profit anyway, but anything we can do to help Julia is good. "Donations" aren't sustainable and can't fund a large software project.
Also it's not hidden, so I fail to see the issue. If the information is in a legal document and the source code, then you know exactly what's going on. There's no shady business.