I'm curious about everyone's opinion on writing "by hand" with a stylus on tablets like the Remarkable, Kindle Scribe, iPad+Pencil, etc.
I like sketching and outlining with pencil and paper, but my handwritten notes are often illegible and disorganized. I know it's partly process and my poor penmanship, but digital surfaces compensate for this with built-in organization, searchability, and easier integration into projects and knowledge bases.
> For an LLM, words are the source, and any meaning is just a byproduct that falls out by accident.
Recently, I've been thinking a lot about context and whether an LLM actually creates a true representation of a concept within its vectors. And for our current usage of LLMs, does it even matter? As models become so large, will the difference even be perceivable to us?
If OpenAI and Anthropic eventually become public companies with trillion-dollar valuations, it will be interesting to see if their company ethos remains the same. With that much purchasing power, it's very tempting to gobble up competitors and raise prices.
The Flash era was the most fun I ever had as a developer. Flash was so ahead of its time, and it still feels like we're slowly crawling back after 20 years. Tools like Rive are helping us get closer, but there was something special about the Flash timeline and drawing tools that made it very approachable and fun to work with.
Director was such a fun app for creating CD-ROM content back in the day! I still have fond memories of learning the Lingo scripting language inside Director to make interactive "multimedia" apps, then uploading them to the web and playing them in the browser using the Shockwave Player. It felt like magic at the time.
That would be great! I usually search and end up on YouTube. Most videos for specific features are longer than needed when you only need to see how to do something quickly.
I recently dropped my cable service (cut-the-cord) after significant price increases over the past two years and switched to a few streaming providers. My household just doesn't watch enough to justify the costs. The plethora of streaming choices is overwhelming right now for consumers, so consolidation is a good thing IMO, assuming it doesn't come with a drop in quality.
As others have mentioned here, the majority of new content recently is mid-level sequels, spin-offs, prequels, etc. It's becoming much harder to differentiate, so people stick with what they know: Netflix, Disney, HBO/Max. I just don't see enough of a market for the other providers to persist long-term (given the high-cost of managing a streaming infrastructure).
I feel like Disney, in particular, should consider spinning off a few of their larger brands, like Marvel and Star Wars, opening them up for licensing revenue and new creative direction.
Blender has such a rich and amazing history! I used it for some hobby projects many years ago, but the UI was very complex and the learning curve was high. Recent versions have greatly simplified the UI and the features feel on par with many of the proprietary industry tools. The future definitely seems bright.
Sure. We're focusing first on converting everything to plain Markdown and using a Git repo to manage the content. Writers can use whatever Markdown tool they prefer for this. (I'm using Obsidian and others are iA Writer.) I have yet to decide on the docs publishing tool, but I'm testing Astro, Vitepress, and Markdoc for publishing. I'm leaning towards Astro since it's very flexible, easy to add small bits of interactivity via MDX, and has a nice collection of themes. VitePress is also very nice, super fast, and very easy to publish. Since only the developers and tech writers need to collaborate on the docs, we're following a docs-as-code approach — using GitHub issues, comments, and pull requests.
> “As we continue to execute on our FY24 plan, we need to also evolve how we work and what we prioritize so we can deliver on the key initiatives we’ve identified that will have an outsized impact in achieving our business goals,” LinkedIn executives Mohak Shroff and Tomer Cohen wrote in the memo.
Is this standard business communication lingo for layoffs?
We're in the same boat. I brought Confluence into our org almost a decade ago — it was the best collaborative wiki tool at the time. Over time the price has increased while the quality of the tool has not kept pace with other options. This seems to be the trend as software companies grow into large "enterprise" providers.
Looking at our Confluence usage over the years, I noticed that we use it primarily as a knowledgebase/documentation tool and less for collaboration. With our on-prem license expiring, we are migrating to a dedicated knowledgebase for our FAQ and frequently changing content and switching to a Markdown tool + Git for our more formal documentation.
Maybe Apple should consider dev editions for MacOS that allows more customization during setup. MacOS is still heavily used by web and mobile developers, so I'm sure this would be received well.
I do end up removing many of the Apple apps, but recently started using Safari, Notes, and Reminders more. Apple does an excellent job making their apps work seamlessly within the Apple ecosystem.
Interesting thesis. When used as intended, web analytics should be only one input to an overall strategy -- not the sole driver for all decisions. But I can see how an organization with KPI's tied to web analytics will lose objectivity -- especially when someone's job performance is tied to the analytics. It's a slippery slope.
I love this quote at the end: "Caring about quality is the heart of craftsmanship. Until you're hooked into those outcomes, micro-optimizing the individual parts is pointless."
Perhaps, as we move towards a web dominated by AI agents, quality will supersede metrics.
Duplo's were the go-to toy in my house for years. The larger size makes it much easier to find pieces in "the big box of Lego" than standard Lego's. Duplo and Lego, in general, have amazing longevity — they were the best toy investment we made over the years. :-).
As an aside, these articles are the gems that keep me coming back to HN.
I completely agree! I loved working with Flash back in the day; it was an empowering tool for me as a developer with little animation experience. It packed so much power into one tool with a complete end-to-end workflow. Over a decade since the "end of Flash" and I still find myself searching for tools that deliver the same capabilities, without the complexity. Things are improving with tools like Rive, but the market still feels fragmented and complex. Flash was way ahead of its time.
How did you organize the new box? Did you use a specific type of organizer? I have a few scattered boxes of cables, wires, and parts that I need to reduce into one "usable" container. Thanks!
In addition to all the great new features, Livewire is now a first-party Laravel package! You can review a summary of the new features here: https://laravel-news.com/livewire-v3-beta.
This is both fascinating and sad. It does feel somewhat reminiscent to the state of HTML (pre-HTML5) before W3C and WHATWG agreed to work together on the development of HTML5. I suppose Google, Microsoft, Zoho, and other large companies that have implemented their own their own layout systems consider their implementation a competitive advantage and would not find it worth the effort to collaborate on a new standard to supplant contenteditable — if that is even possible.
Good points! As someone who uses both ORM and raw SQL (I actually really like SQL as language) I sympathize with both sides of this debate. I prefer the readability of ORM in my models when developing, but closely monitor and optimize for N+1 and other inefficiencies, when needed. "When needed" is never cut-and-dry, but I try not to optimize too early. I actually tend to start new projects from the database and will scaffold with factories, seeders, and raw SQL queries to get a sense of the data model prior to coding.
ORM's such as Eloquent in Laravel also have some nice methods to resolve N+1 and perform lazy loading, but it's always tradeoff.