chrysoprace
chrysoprace on Hacker News
Well consider this, if you end up liking Vim you'll almost certainly want to have Vim keybindings in everything you use. :)
I learned Vim because I didn't like using Nano to edit server configs, and ended up sticking with it because I wanted to ditch my mouse in my workflow for fear of long-term RSI development.
Vimtutor is a built-in command in Vim and Neovim, and I personally wish I started with it since it's super helpful. You only have to learn as much as you need to, to become productive and then you can progressively get more advanced with macros and piping the file contents to a command line tool like jq.
My 2018 (maybe 2017?) 13" 2-in-1 HP Spectre x360 was one of the nicest pieces of hardware I've ever owned (albeit not that powerful by today's standards), it's just a shame that Windows was so inadequately designed to support the hardware.
I definitely think that a distinct mode is needed though, the inverse of attaching a keyboard to an iPad to make it more desktop-y.
I think it's really cool that you built the game around a mod API - I think all games should do this, and I love projects that were built for the love of the craft.
If you liked the look of Cube World but not what it became, you might enjoy Veloren[0], which is a free GPLv3 effort to build a game inspired by Cube World.
[0] https://veloren.net/
I don't think that's the case. This is from anomalyco, the company who made sst.dev. Crush is from Charm. I think OpenCode may have originally been written in Go but nowadays their codebase is TypeScript.
Edit: I'm missing some context others have pointed out.
I figured Slack referred to slack in task time estimation i.e. the amount of extra time allowed in a task. Collaborating on Slack would count towards that time.
At the expense of your privacy, potentially acting irrationally on your behalf, with the inherent weakness of being able to be prompt injected. All of that is not even to mention the grey area of who is responsible when your agent breaks the law.
These aren't hypothetical, and in the hands of non-technical users let alone technical users, they have are far too unpredictable.
Personally, I think the worst possible use case is the one that's being pushed for; personalised agents.
I think a much better use case is one where it's not visible to the user at all, like spam filtering or helping an accountant do their monthly run in a few hours rather than a day. To me, that's likely a much better use of AI than trying to shove a chat interface or agent harness into an existing app.
That being said though, I did see a startup in my area basically offering a Resend/Mailchimp competitor as a Claude plugin, so maybe it'll just be integrations to their existing chat interface.
We can do both - like running your air con while the sun's out (with solar panels) and turning it off at nighttime.
It's better in just about every way, and if you have a copy of TA (such as from GOG), you can load the soundtrack from TA into BAR's music folder and it'll change the soundtrack to the TA soundtrack.
It's very sad. I was excited about Deno from day one, and I wanted to see it succeed.
Deno's ability to run TypeScript files - stripping types - was arguably implemented in Node because of Deno. The consolidated tooling approach was a good attempt at solving tooling fragmentation that Node suffers from.
I think for Deno to succeed, it would've had to have been under a non-profit and maybe that can still happen.
The Bevy team are doing amazing work and it's great to see it being worked on all the time. I'm not a game developer, but it's interesting to see it listed in some jobs for companies building simulations.
Factory games like Satisfactory and Factorio see players with thousands of hours on the games and those have static HUDs that would likely burn in.
I have many criticisms of Apple and their hardware, but the Mini-LED screen on the M1 MBP I had at a previous job was stunning. I was in the market was a Mini-LED monitor last year and ended up settling with an IPS LCD in the end due to the lack of premium high-refresh 1440p options at the time.
I wanted Deno to succeed to have a single standardised toolchain, but with Deno having its own APIs you'd effectively have to architect your application to be a "Deno app" and it created two different ecosystems. The best way to make your app portable would be to use the provided Node APIs, cutting a lot of the value from Deno.
Location: Brisbane, Australia
Remote: Yes, or hybrid locally
Willing to relocate: Only to Denmark (no sponsorship required)
Technologies: Node.js, TypeScript/JavaScript, React, Next.js, Svelte(Kit), MySQL/SQL Server/PostgreSQL, AWS, Apache Kafka, GitHub Actions, C#/.NET Framework.
Résumé/CV: Available via email
Email: Available in my profile
GitHub: https://github.com/c-kirkeby
Full Stack Software Engineer with 10 years of delivering end-to-end features in loyalty environments, digital marketing applications, serverless event-driven systems via Kafka and Point of Sale integrations. Strong background in software testing and test automation. Experience maintaining greenfield and legacy applications.
Is there a way to implement Effect without it becoming a leaky abstraction that takes over your whole app? Presumably you'd have to create an entire abstraction layer with strict boundaries, such as nestjs does with RxJS Observables, but even that has problems with leaking Observables when you need to hook into the framework's lifecycle.
Been using SvelteKit 3 on a couple of personal projects since the beta and haven't had any issues. The best part is that it barely introduces new features and instead improves on existing features.
The idiomatic way to do data fetching in stable SvelteKit is via load functions.[0]
They still do a good job and allow you to cache the results and invalidate that cache, but they are at a route/layout level rather than at a component level, which is what remote functions solve.
[0] https://svelte.dev/docs/kit/load
They're effectively ready to use even if experimental; the migration path is typically pretty painless when features are stabilised and the codemods get you most of the way. There's a couple of missing features for them but if you don't need those then it's not a problem.
It's still full Android. You could get part of the way there by just installing a different launcher.
The USB-C port for charging is on the battery itself; their store diagram doesn't show if the battery itself can be disconnected for power passthrough.
That makes more sense then. I did not realise that US electronics prices were before tax.
Oh I'm just not a lisp fan, and with it being a bespoke language for Emacs it has the same issue as VimScript: you have to learn a language just for configuring your editor. With something like Lua, it's simple to learn and I can use that knowledge for things other than just configuring my editor.
With neovim's cult following I figured it was only a matter of time before somebody made a similar rewrite for Emacs, even if it does smell of vibe-coding based on the README.
I don't see any notes in the README about alternative scripting engines, elisp was always the main that turned me off from emacs. Does anybody know if they plan to add something like Lua?
Aussies are getting it at a premium, too.
USD$1059 (256GB) should be AUD$1483, retailing for AUD$1609 - a AUD$126 premium.
USD$1299 (1TB) should be AUD$1819, retailing for AUD$1969 - a AUD$150 premium!
Beat me to it, I was just about to post this. It's a really cool breakdown of what goes into supporting and modernising such old open source software.
I use Firefox, but Mozilla is increasingly eroding user trust and being primarily funded by Google to avoid a monopoly does not give me confidence either. When Google implement an anti-user feature, Mozilla have to begrudgingly implement it, and that is not a healthy ecosystem. There's a good chance that I'll move from Firefox when Ladybird reaches feature-parity, but they'll likely fall into the non-standard standards (Chrome-pushed features) trap all the same to avoid having sites break.
I don't know how we solve this, other than to hold Google accountable, but that in turn hurts Firefox. At least in that case we'll hopefully have Ladybird as a truly independent browser.