Hacker Newsnew | past | comments | ask | show | jobs | submit | koolala's commentslogin

It doesn't say that. Your thinking of dynamically linked code. In-memory makes it sound like two programs loaded into the same stick of RAM.

What's more dynamically linked than something unexpected the user requested, but it was brought forth upon demand?

It means a dependency for the program not data for the user. Uploading a GPL file to Dropbox doesn't make everything on their server GPL that would be crazy.

At this point, I would argue that a jury wouldn't be able to tell the difference.

Can you quote the part of the license your talking about?

Could this let you conpress models into lossy systems like JpegXL?

Yes ! here I get x20 compression on the bunny for a very correct output. (pip install flatpoints[viz] pyjpegxl)

import flatpoints as fp

import pyjpegxl

import os

#============ Raw point cloud =============================

xyz = fp.load("bunny") #Required format: numpy array, (N, 3)

#============ Fit the flattener ===========================

single_face = True #Or false -> two images (left + right)

flat = fp.Flat(xyz, single_face = single_face)

#============ Build one (single_face) resp 2 images: ======

images = flat.to_image(xyz) #(1, n, n, 3) or (2, n, n, 3)

left_image = images[0] #(n, n, 3), right_image = images[1]

#/!\, normalisation, needed for pyjpegxl:

b = xyz.min(axis = 0)

a = xyz.max(axis = 0) - b

left_image_normalised = (left_image - b[None, None])/a[None, None]

#============ Compression, Decompression ==================

pyjpegxl.imwrite(f"compressed.jxl", left_image_normalised, quality = 98)

_, image_decompressed = pyjpegxl.imread(f"compressed.jxl")

xyz_decompressed = a*image_decompressed.reshape(-1, 3) + b #basically, that's it.

#============ Visual inspection ============================

_ = fp.Flat(xyz_decompressed, single_face = single_face).plot()

#============ Memory saving ============================

memory_before = xyz.nbytes

memory_after = os.path.getsize('compressed.jxl')

print(f"Initial memory: {memory_before / 1024:.2f} KB")

print(f"New memory: {memory_after / 1024:.2f} KB")


We still badly need a replacement for Glitch.com. There are no free dynamic server hosts anymore.

I vaguely remember glitch.com. How is it different from stuff like Lovable, base44, etc.?

Can't you fix this scaling by chunking the entities? So not making one massive 10,000 thing entity but instead breaking it up into entities that group 500 things?

Of course you can, and you can also make it so that if UI changes, instead of having every single entity rerender, only the changed entity would rerender, and you can have a library that manages the changes or "dirty" state of these entities reactively.

And that's why React exists.


Almost every GUI toolkit does this, it’s nothing React specific. And with the browser you have to know all sorts of complexities to know what it’s actually doing (is this change going to cause a full layout, full paint, etc.)

Personally I think most of the abstractions we’ve tried around GUIs don’t work, and old school frameworks like AppKit are better. They just need some DX love since programming has evolved so much.


Doesn't that need a whole new framework with other downsides but the first option lets you use it with how it is designed?

Isn't being able to self host it on your company network a big important feature? Like for all the non-public branches and projects you keep internal. Gives you the same UX for everything.

This sounds pretty annoying though: https://docs.gitlab.com/administration/license_usage/



Is it more expensive?


Than Gitlab?

I'm not sure, you'd have to check their pricing pages.


It doesn't say does it? For self-hosted commercial use? Wish either were open-source.


I'm sorry, I think you're trying to make a point and I'm not quite following it. Yes, Github Enterprise requires a license.

Github Enterprise is $21/user/month: https://github.com/pricing


Oh nice that $21 includes self hosting. The point we were talking about before was the difference between the two and gitlab can let companies host it for free.


Gitlab Enterprise is not free (it costs more than Gitlab Premium, cloud, which is $29/user/month), and companies that would want to self-host something like Github Enterprise are not hosting the free version of Gitlab - so these are not comparable. For example, SAML SSO and audit streaming (SIEM support) requires paying.

As best as I can tell, your argument is "Github costs money which is bad" and I don't find it particularly convincing. Companies need to make money in order to continue producing products. That's why Gitlab sells their product too.


What makes those two features so important when using gitlab internally? Would Roku really need those features for its devs? To me they don't seem like things you worry about with normal Gitlab / Github anyways and all kinds of teams use it fine.


I'm sorry but if you don't think SSO and audit logging are important to companies, I'm inclined to believe you haven't been working long. These are typically table stakes for compliance reasons. Auditability and security of your code is incredibly important (this is your supply chain!) Yes, Roku would care. And yes, GitHub (and Gitlab!) offers these things.


Couldn't this be done by wrapping a open source service around gitlab or a git interface for it so it could be done for free?


That is important or critical in some companies. But that's surely not what they meant by fitting their "mental model" better.


The solution was simple and always possible. It is to make it only work for same-origin content. Aka it can't work for ads or closed source external web content.


Are comment threads like this 'social media'? Do we need to get sober from reading other fellow people's opinions on information?


This video is iconic


The new responsively-sized iframes standard is an exciting one for me not mentioned. It's finally a step beyond the original frames and framesets. It will let us design sites out of iframes as building blocks instead of needing to use web components. Websites made out of websites.


After all these years they still haven't even recognized what they did was wrong so I think their summary was charitable.


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

Search: