Hacker News new | past | comments | ask | show | jobs | submit | awongh's favorites login

Ableton has like a 3 month trial and honestly the stuff it comes with out of the box is way more than enough to determine if you want to continue with such a hobby or if it's not something you'd be interested in long term. The tutorials are plenty and easy to follow as well.

I use Reaper as well, but it takes a while to get that "useable" for modern(ish) music production. The benefit is there's plenty of free virtual instruments/VSTs to download. All of them have downsides though as does reaper itself. In Ableton I can make an EDM track relatively fast given the out of the box presets - especially synth drums - but in Reaper using a free VST like HELM makes it kind of a pain to use. YMMV.

No matter what you choose, I do HIGHLY recommend downloading Spitfire LABS though - the free instrument packages are massive and highly customizable. It's truly amazing.

Here's some good VSTs for Reaper:

https://plugins4free.com/instruments/ (when the site works)

https://web.archive.org/web/20181203014924/http://sonic.supe...

https://guitarclan.com/best-free-vst-plugins/

EDIT: oh also trying to master a track in Reaper with free plugins is frankly pretty bad for a beginner vs Ableton's preset limiters and other utilities. The Cuckoos plugins are messy to deal with in my opinion.


For just getting started I recommend collections:

1. Ideas That Created The Future[1]. It's a collection of fiftyish classic CS papers, with some commentary.

2. Wikipedia's list[2].

3. Test of Time awards[3]. These are papers that have been around for a while and people still think are important.

4. Best paper awards[4]. Less useful than ToT as not every best paper is actually that good or important, and sometimes the award committees can't see past names or brands for novel research.

5. Survey Journals[5]. Students often get their research started with a literature review and some go the extra step to collect dozens of papers into a summary paper. I subscribe to the RSS feed for that one, and usually one or two are interesting enough to read.

6. Citation mining -- As you read all these, consider their citation list as potential new reading material, or if an old paper leaves you wanting more, use Google Scholar to find a papers that cited what you just read.

[1]: https://www.amazon.com/Ideas-That-Created-Future-Computer/dp...

[2]: https://en.wikipedia.org/wiki/List_of_important_publications...

[3]: https://www.usenix.org/conferences/test-of-time-awards

[4]: https://jeffhuang.com/best_paper_awards/

[5]: https://dl.acm.org/journal/csur


Air resistance is proportional to v^2.

My dad told a story once where he was driving out west borrowing one of his brother's cars with a broken speedometer. After he got back he said to his brother, "the car just seemed to top out at a certain point" and his brother said "yeah, that's about 85 mph" (the national speed limit was 55 mph at that time). So at 85 mph the air resistance equaled the force the engine could apply and the car wouldn't go any faster.


Deno code is really close to browser code. If you have ESM code that runs in the browser and doesn't need access to the DOM then it's a good bet it'll run on Deno, and vice versa. They use web standards for most things, and anything proprietary is put on the Deno global object. For standards that need adapting to work outside the browser, they're working with Cloudflare and others on WinterCG, which is defining a common baseline for these non-browser runtimes.

> I just don't think it's possible to create an ethical review platform on the internet.

I definitely agree that it's a hard problem, but I would be wary about saying it's impossible. This shouldn't be rocket surgery!

> And if your goal, as the owner of FooBar Business Reviews, is to maximize your profits

What is that wasn't your goal? Perhaps such a site could be a non-profit...


Life should not be a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming "Wow! What a Ride!

Based on Salesforce's handling of the April / May security breach / incident I would not recommend Heroku, not even to other developers who understand risks and would just use it for hobby / throwaway projects.

Gonna have to test all the meme alternatives soon, fly / render / glitch / porter.


After killing both nuclear and russian gas I wonder how they'll do.

French politicians are already calling for people to reduce their home temperature by 2 degrees C to not be impacted by the Russian gas being cut off, and France uses way less Russian gas than Germany. With German electricity already being twice as expensive as France I'm worried for my 2022 electricity bill


Greatly successful projects often have horrible(from developers perspective) codebase that barely doesn't fall apart. They call it technical debt and fix il later when things stop moving fast.

I think it's happening because successful projects focus on the product delivering on the reason it exists(i.e. facilitate file transfer in the most intuitive way possible) and to do that quickly as possible for the lowest cost possible engineers hack together solutions derived from the existing tools without focusing on the technical or ideological perfection. Also, they cannot focus on the technical stuff anyway because to needs and direction change all the time, therefore it's not possible to crystallise an optimised and well built solution anyway.

What Microsoft or other companies do is to built versatile tools that that engineers can bend and stick together to accomplish the tasks in hand very quickly and if it looks like the thing is here to stay they can design and implement an optimised and elegant solution later on. At first it may look ugly but it is usually an original work done by domain experts who are exploring technical solutions to the problem in hand. Once the solution is found, experts in computer programming and architecture can step in and make it elegant but that last step is not needed for the wast number of solutions.

An example for this is UK's covid case tracking early on. Apparently they quickly implemented a central Excel spreadsheet that would collect the CSV data sent from the test centres. Unfortunately, the solution they implemented was way too hacky and they lost data once they reached the limits of the spreadsheet format they have chosen. Had they chosen a better format, their solution would have worked up until much higher scale and once they have a better understanding of the nature of data collection etc. then they could have implemented a clean sheet solution with "perfect" code and scalability, maybe years later for the future pandemics and write blog posts about the enormous challenges and their ingenious solutions. They couldn't have start by firstly building the perfect data collection solution because they wouldn't know how things will pan out and if they tried to force their way(i.e. mandatory formats by the tests centres) it would have been too big of a projects.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: