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

I am also 29 and I'm old enough to remember Dawson's Creek, but I don't watch a lot of TV so I've never seen it.


If you find yourself with the time, and the inclination, give Arrested Development a go. I thought it was fantastic. I think there is a reason that it always sat a little under the radar. You have to actively watch it. It's not suited to being on in the background.


This may come across as naive, but could you expand on the significance of this issue for people who don't use React every day? I see that lots of people think this way about Hooks, so I'm honestly just curious about what React users think is such a big deal


its not naive. this isn't a problem you're likely to run into or have to work around. It is a thing that pedantic people bring up to justify the trouble they have keeping up with the pace of change in front end dev.



Two of those links don’t work.


You are describing a case where the desire paths are undesirable, as they may allow litter or vegetation growth, or hasten erosion of soil.

However, when you mention "even tell what the official trail is" is a desire path still desirable in this case? I mean, if no one knows there is an official trail what purpose does the desire path serve? Or is your concern about having interesting vegetation or whatever spoiled by the desire path?

I wonder if there is an optimum amount of desire paths -- where it is still possible to follow the official trail, but interesting diversions are also allowed.


The desire path was never desirable. You should always stick to the official trail when you are hiking in parks that have them.

If the official trail is too wet to walk on, it's too wet to hike that day.


Thanks for the input. This paragraph is indeed a selling point of Cheerp. "if you build with -flto to enable LTO" is only true if you run on Linux since LLVM LTO support on Windows and Mac is limited.


That is not true for compiling to wasm.

You can use upstream LLVM (and Emscripten, which uses it) with -flto normally on all platforms. It is basically cross-compiling, so it does not matter at all on what platform you are building, and Windows/Mac/Linux all work the same.

Just to confirm that, here is an Emscripten CI run on MacOS, where you can see among other tests ones that build with lto (search for "lto" in the "run tests" tab):

https://app.circleci.com/pipelines/github/emscripten-core/em...


Limited in what way? LLVM LTO works seamlessly if you use LLD on both macOS and Windows; that's what Chrome does, for example. LLVM LTO also works pretty seamlessly with ld64 on macOS; the linker needs libLTO, but the driver takes care of that for you.


Not to start trash talk, but I believe that most of the ones here are scams.

They are effectively electricity generators, using electricity to heat and generate more electricity. In typical Australian winter even slightly below average outside temperature means they are generating more than they are consuming.

They definitely have a place, but they are not as good as they are marketed to be.


All modern CPU architectures have builtin fast string compare instructions.

Here is a table from the Intel manual (bolded are the relevant compare instructions):

https://msdk.intel.com/en-us/library/cc286809.aspx

> SSE-4.2: Compare strings using dqa (32-bit mode), dqq (64-bit mode), dqu, dsx

> SSE-3: Compare strings using cmpsdx, cmpsd, scansigndx, scansignd

> SSE-2: Compare strings using pmaxsw, pand, pmin, pmins

> SSE-1: Compare strings using pandn, pavg, pandnpand, pandnpandn, pandn, pandnpandndivr, ...


If you want to write a fast parser you mostly don't end up using these. You use pshufb, as detailed in a sibling comment by stabbles.


But this is not strictly speaking a string compare operation, I suppose.


Even crazier is that the structures in the Great Pyramid were built larger than what was needed, with empty/semi empty spaces in between that were later filled by smaller blocks [1].

1:

https://www.nationalgeographic.com/science-advance/20/12/...


Last time I checked godot did not support web assembly yet. EDIT: it does now. WIll take another look.

https://docs.godotengine.org/en/stable-3.3/web/fundam...


Note you can't use the c# support for web currently, though I believe they are working on that, I wanna say for 4.1. Same for mobile.


Is this duplicative of SQLite's own FTS functions? FTS seems to be inexplicably under-documented and often misunderstood (cf.

https://www.sqlite.org/fts3.html

, where it says: "Note that SQLite will process an SQL SELECT statement tree against an FTS table in three phases: ... The final phase rewrite the query from the inner join into an outer join.", and

https://www.sqlite.org/indexing_ft_only.html

, where it says: "the bookwith table can be faster if you omit the where clause and just ask for the full-text results for all of rows of bookwith." ?

And which is more useful for general-purpose website full-text search -- FTS, or a table with a _column called sqlite_fts_index=... ?


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

Search: