High level programming languages were conceived by humans and for humans. Will AIs in future better use their own languages, or maybe even output machine language directly?
It works until it doesn't. And it can stop working very fast. Which is the scary part. But then it also depends on entry point. If you entered early even going down say 40% or 60% might not make you go red.
So if you want to invest in the top companies, you either need to think they won’t change anymore, or you need to find when to buy and sell.
Index funds solve this problem for you, albeit with slightly lower returns in the short term.
> So a viable strategy would be to only buy the best 7 stocks? Like the Dogs of the Dow, but reversed? (The Gods of the Dow?)
Or go with a NASDAQ 100 index: you'll generally get higher returns than the S&P 500 or Russell 3000, but you'll also get higher volatility. How well would you sleep at night with drops of -20% more often?
This is probably ok if you consistently sell stuff that exits the top7 and buy stuff that enters, but I kinda doubt it's all that much better. Same as the s&p500 and the Russell 5000 have really similar returns.
You'll be more exposed to screwing things up when companies enter/leave.
Isn't the opening paragraph perfectly fine as it is? It was the first thing I read and I feel like I understand exactly what it is:
> Seed is an interactive software environment. With it you can create and use computer programs in many ways. It is based on the Common Lisp language and runs inside the Web browser, allowing you to build software on a local or remote computer system, and it can present programs and their output using a wide variety of display modes.
An environment for creating programs, that you can use locally or remotely, and it can show programs and data in various ways.
Sort of. It'd be really great to get a feel for what it'd be like to use without having to mess around with npm and sbcl. Plus the most recent commits to it are 6 years old... while this isn't uncommon in the Lisp world (that community has a pretty solid "we don't need to change this anymore because the library is complete" philosophy), when bringing npm into it I definitely have concerns that this would be a waste of time to try to get running because of how many times the wheel has been reinvented in that world.
A couple of screenshots would definitely help me assess whether or not it's worth the time to try to get this running (and figuring out the probability that it would be that it's something I'd love using).
When the first sentence on the page is "This website requires Javascript to be enabled.", I leave; but not before looking at the source and discovering a relative monstrosity, unlike the original PuTTY site which is almost pure content.
I'm sure it's a great piece of software, but sometimes, the simpler is better. I used PuTTY for a decade or so, and while it was kinda ugly and clunky, it's very beautiful and perfect because of its imperfections.
I agree in general, but this project HAS releases; At least, it had until a certain date. So if you jump to the releases page, it gives the impression that the project is now dead. If they have abandoned that model, they should at least write it somewhere.
In the 90s, Book Stacks (books.com, eventually bought-and-destroyed by amazon), in addition (or before?) having a website, had a text-only online bookshop via telnet. I bought some titles that way. It was pretty cool!
Hm. I actually can’t bring myself to watch the series through again because I know I won’t enjoy the end.
I remember I was living with my roommate at the time and we’d watch the show religiously as episodes came out. At the end we both couldn’t help but laugh at how bad it became, haha. We really didn’t want it to be true, but… It was cheesy as hell. I won’t watch it again.
reply