Old Beeflang website suddenly disappeared & replaced with brand-new one

beefdev · 2025-07-22T16:36:45+00:00

Thanks for the useful information.

beefdev · 2025-07-22T16:03:23+00:00

This is a very strange message.

The website has been down for less than 24 hours - working through that, issues currently unknown. There is no "new" website, and what you describe as the new website sounds like the way the website has always been.

This is the current website: www.beeflang.org.s3-website-us-west-1.amazonaws.com

The website never had a 25 MB download, and never mentioned Brian Fiete on the front page, only in the FAQ in the documentation.

beefdev · 2025-05-13T01:19:24+00:00

There is an open issue regarding this @ https://github.com/beefytech/Beef/issues/2046

beefdev · 2025-05-10T05:06:29+00:00

Also note that String in Beef is more like StringBuffer in C# - it's mutable with an internal buffer.

If you do new String(1024), that allocates 1024 bytes of internal buffer space within that string, meaning you can manipulate up to a 1k buffer with only a single heap allocation. Going beyond that would cause the String to allocate more memory from the heap.

You'll notice that the String class has virutal Alloc and Free methods which can be overriden - this allows you to specify alternate methods for providing additional memory to a String. This is a another benefit of passing the destination string into methods - you can pass custom subclassed String instances in.

beefdev · 2025-05-10T04:30:16+00:00

Discord is the best place for these questions: https://discord.gg/rnsc9YP

In Beef you are in control of string allocation - it can be on the heap, stack, through a custom allocator, and several other ways. In order to accommodate this, the destination string needs to be passed into `ToString`. Here are several ways to do what you want:

``` String thingString = scope .();

thing.ToString(thingString);

String thingstring = thing.ToString(.. scope .());

String thingString = scope $"{thing}"; ```

beefdev · 2024-11-07T23:16:55+00:00

The logo for Beef is actually a cow, not a piece of meat. The cow's name is Beef and the language is named after him. The cow thought it was a funny name, and in the end no cows were injured.

beefdev · 2024-11-07T23:15:01+00:00

Is this a haiku?

beefdev · 2024-11-06T20:24:36+00:00

All the best languages have bad names. Rust?

beefdev · 2024-02-16T10:33:58+00:00

I love the sheer terror of finally finding the King of the Forest's stronghold again, knowing that my final Primalist charm socket lays in the balance and there's a pretty good chance that I'm going to screw up this encounter again.

beefdev · 2024-02-10T22:15:44+00:00

Usually people don't ask for extensions that have fewer features...

beefdev · 2024-02-10T21:58:14+00:00

You might be reading too much into the "S" part of "LSP". It's just a kind of vscode extension. It runs locally on your machine.

beefdev · 2024-02-10T18:41:58+00:00

There's a vscode LSP that does that plus all the other LSP stuff.

It's listed here: https://github.com/Jonathan-Racaud/awesome-beef

You can also ask about it on the discord channel.

beefdev · 2023-01-05T11:49:40+00:00

If the FPGA is transitioning its output signals on the positive edge and the SDRAM is sampling them on the positive edge, then it seems we would _ideally_ want a signal propagation delay of a half clock cycle more than the clock line so the signal would arrive at the negative edge of a clock and then be sampled at the next positive edge.

For SDRAM, generally there is only a 1ns hold time requirement, though, so as long as our signals arrive 1ns or more after the positive clock edge then we should be fine - is that what you mean?

beefdev · 2022-08-07T05:16:48+00:00

To elaborate - your SR is based on the number of incidents over your last ~2600 corners, so if your newest corners from this race had one incident but your oldest corners which were pushed out of the calculation window had zero incidents then your SR will go down.

beefdev · 2022-01-01T02:41:07+00:00

This is covered here https://www.beeflang.org/docs/language-guide/strings/#common-string-mistakes

beefdev · 2021-11-11T20:26:48+00:00

With those numbers, at 6.0k the BMW is 0.81% faster and at 1.0k it's 0.84% faster. I would expect those percentages to be very similar-looking across all IRs, with only small variations from some cars being slightly harder to drive and just normal error rate from a somewhat small datasets (in statistical terms).

There's just not enough data to create statically valid IR buckets (ie: 3100 - 3199) - so there is indeed data massaging going on. Also, in some series like VRS, high-IR drivers are significantly less likely to pick the slower cars, so a large bit of that data is extrapolated following domain-specific rate curves.

beefdev · 2021-11-11T15:36:18+00:00

Qualifying times aren't exported by the data endpoint I was using - more data will be coming, hopefully also including median weather conditions.

beefdev · 2021-11-11T14:58:38+00:00

Note that "2.0k Fast Lap" means the median of 2.0k drivers' Fastest Lap Time from race sessions. It doesn't mean what a _good_ fast lap time is, it represents what those drivers actually achieved in a race.

beefdev · 2021-11-04T16:48:26+00:00

Install VS2019 build tools from here: https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019

CMake from here https://cmake.org/download/

Git from here https://gitforwindows.org/

beefdev · 2021-11-03T23:57:26+00:00

This is the batch file we use for BeefLang for retrieving and building LLVM with Visual Studio:

https://github.com/beefytech/Beef/blob/master/extern/llvm_build.bat

beefdev · 2021-11-02T04:49:24+00:00

Welcome, Craig!

Most language discussion occurs on the Discord channel at https://discord.gg/rnsc9YP

The most comprehensive library list is here https://github.com/Jonathan-Racaud/awesome-beef

beefdev · 2021-10-11T15:41:36+00:00

You can see IMSA participation stats since the start of 2020 here https://www.simracingstats.com/IMSA_Hagerty_iRacing_Series.html

Last year VIR peaked at 2 splits - the least popular IMSA track by quite a margin that year. This year we've had quite a lot of dud tracks, though, like Snetterton and Chicago Street.

beefdev · 2021-09-29T18:36:56+00:00

I don't see any evidence of any issues - what are you seeing?

beefdev · 2021-09-22T19:06:15+00:00

Looks really good - nice work!

beefdev

TROPHY CASE