HN user

azmenak

178 karma
Posts4
Comments37
View on HN

From my personal testing, running various agentic tasks with a bunch of tool calls on an M4 Max 128GB, I've found that running quantized versions of larger models to produce the best results which this site completely ignores.

Currently, Nemotron 3 Super using Unsloth's UD Q4_K_XL quant is running nearly everything I do locally (replacing Qwen3.5 122b)

As someone who has spent a good time of time working on trusted compute (in the crypto domain) I'll say this is generally pretty well thought out, doesn't get us to an entirely 0-trust e2e solution, but is still very good.

Inevitably, the TEE hardware vendor must be trusted. I don't think this is a bad assumption in today's world, but this is still a fairly new domain and longer term it becomes increasingly likely TEE compromises like design flaws, microcode bugs, key compromises, etc. are discovered (if they haven't already been!) Then we'd need to consider how Confer would handle these and what sort of "break glass" protocols are in place.

This also requires a non-trivial amount of client side coordination and guards against any supply chain attacks. Setting aside the details of how this is done, even with a transparency log, the client must trust something about “who is allowed to publish acceptable releases”. If the client trusts “anything in the log,” an attacker could publish their own signed artifacts, So the client must effectively trust a specific publisher identity/key, plus the log’s append-only/auditable property to prevent silent targeted swaps.

The net result is a need to trust Confer's identity and published releases, at least in the short term as 3rd party auditors could flag any issues in reproducible builds. As I see it, the game theory would suggest Confer remains honest, Moxie's reputation plays are fairly large role in this.

iPhone Pocket 8 months ago

Seeing all the nerd brains of HN implode trying to understand this. This is what happens when the tech and fashion worlds overlap for a moment.

To contrast, in my early days of options trading with Interactive Brokers, they had closed a spread ~10 minutes before expiry at a loss, which turned profitable 8 minutes later.

Contacted support, and they responded within 2 minutes explaining exactly why this had been done (risk profile at the time, and insufficient margin to cover). They answered all my questions and even explained what I should do to mitigate this issue going forward.

While still a ways away, its great to see progress on this front. After SABs were disabled, the use cases and power of WebWorkers shrank considerably.

Very excited to dive back into some WASM/WebWorker projects that got abandoned due to performance limitations.

Electron 9.0 6 years ago

Are there any other release notes? Surprised to see just 2 (seemingly?) minor fixes merit a major version bump

We use JIRA to track our product development with a fairly large team (including 17 engineers) and while JIRA has its pain points, it does have integrations with development workflow.

In our setup, after a PR is merged in Github, the ticket automatically moves to the next “step”, in our case “Ready for QA”.

Beyond that there are automation workflows that accomplish much of what you are asking for here, the issue is that these are complex tools/flows that require a lot of up-front work and continuous maintenance which might not be worthwhile for all teams.

Also IANAL, but its my understanding (at least under common law here in Canada) that the doctrine of privity of contract should apply here. Since the ticket purchaser only has a contract with Ticketmaster/Live Nation they should not be able to sue the 3rd party event provider, and rather are only left with the option to sue Live Nation.

d1g1t | Senior Software Engineer, Front-End | Toronto, ON, Canada | ONSITE Full-time

d1g1t is a digital wealth management platform powered by advanced analytics and risk management tools that offers transparent portfolio management services to professional advisers and their individual investors. Our goal is to empower wealth management firms to transition into a new business model that is driven by technology and analytics, and provides a richer experience for their clients.

We are looking for an experienced JavaScript (Typescript) developer who is proficient with React.

On the front-end our tech stack on the front-end includes React, Typescript, Redux+Sagas, Swift (iOS) and Kotlin (Android)

We are a team that is passionate about our work, and we strive to maintain the highest standards for code quality. If you are looking to work on genuinely difficult engineering problems in the front-end space in an engineering focused organization, this is the job for you.

If you’re interested, please reach out at adam.zmenak@d1g1t.com

I've been neglecting the maintenance of the package "react-stripe-checkout" for a while and though this would be a good time to finally bring it up to date, but it appears the new version of checkout was created with a very different use case in mind. Single page, JS rendered apps don't really fit the model, and should probably use legacy Checkout or Stripe Elements.

d1g1t | Senior Front-end Engineer | Toronto, ON, Canada | ONSITE Full-time

d1g1t is a new digital wealth management platform powered by advanced analytics and risk management tools that offers transparent portfolio management services to professional advisers and their individual investors. Our goal is to empower wealth management firms to transition into a new business model that is driven by technology and analytics, and provides a richer experience for their clients.

We are looking for an experienced JavaScript (Typescript) developer who is proficient with React.

On the front-end our tech stack includes React, Typescript, Redux+Sagas

We are a team that is passionate about our work, and we strive to maintain the highest standards for code quality.

If you’re interested please email me: adam.zmenak@d1g1t.com

Had a very similar experience with RN and also learned iOS swift as a result.

It felt to me like I was fighting with the framework every step of the way, swift on the other hand is an absolute joy to work with.

We use keyboard controls in our app (vidhub.co) to control media, looks like a Safari 11 user will no longer be able to just hit a key to start a video if Safari's "automatic inference engine" chooses to block us.

I do almost 100% js dev these days, and I've been switching back and forth between Sublime and VSCode for the past few months. The one major issue I have with VSCode is lack of completions for strings and words which Intellisense doesn't understand. Sublime's CodeIntel dose an excellent job of picking up all the "words" I've used in open files and saves me a lot of typing and typos.

Maybe there's some config I'm unaware of, since VSCode's site does mention "words" as a type of completion, but I've never seen it work for js files.

As a developer and an Apple user for last decade, this has certainly been the most disappointing Keynote I've ever seen from Apple. I do think, however, some of these concerns are overblown.

If you're a VIM user and haven't tried overriding the Caps Lock key to be an Esc key, you should give it a try, it has made VIM a much better experience for many people.

On the memory side, doing development work I can hardly think of a time when 16GB was limiting on the RAM side, and I hardly notice the performance hit when using swap on the incredibly fast SSD.

And the processors have definitely improved, I'm currently running a 15" MBP Late 2013 at 2.0GHz. The new base models are starting on newer architecture at 2.7GHz.

Having said that, I'm still not sure whether I'm going to be upgrading any time soon...

First off, congrats to the LastPass team! You guys have built an awsrome product and company.

My hope now is that LastPass won't go down the same path as Meldium, after they were acquired by logmein; the product went downhill very quickly.

In the case of Meldium, it seems they were trying to improve the UI by improving the design at the expense of functionality. It feels like LastPass is in a similar position now.

China 11 years ago

There are a lot of great issues discussed here, and I'm going to say that most of it is valid and on point.

After living and working in SF, I moved to china 6 months ago and have come to understand that Chinese compared to US simply have hugely divergent values. And they work hard. From a very young age, they are conditioned to do so; and with 1.4 Billion people competing, there's no other option.

The US is still, and should continue to remain the focal point of innovation. I find China to be so far behind in this area, I don't think there is any hope of catching anytime soon.

I say this because, much of the money in China is grounded in old and dying business principles. The new generation, those in the country's "top" business schools, are being taught dated ideas which don't promote innovation at all.

I do agree though, China will continue to grow and the West will find a way to coexist. But I'm still not trading my USD for RMB just yet.

Edit: typos