SimulaVR / SimulaVR/Simula

Is this project dead?

Open
#180 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Haskell
Stars
3.2k
Forks
111
PR merge metrics
No merged PRs in 30d

Description

The hardware side seems to be posting updates reguarly on twitter, but this repo hasn't been updated for months. To be brutally honest, this project isn't even remotely close to ready. I experience frequent crashes and issues, even what you expect to be simple day to day operations don't work smoothly. Performance leaves much to be desired, mouse side buttons don't work, many programs straight up don't open correctly, things being open on the desktop prevent them from being opened. There is no persistence between sessions, no real window management, and not even a basic ui. Unless this project isn't really open source and there's some secret repo with a functional OS hidden away, I can't imagine this will be ready for the planned launch.

It really sucks because I want this to work so bad. I can see the outline of a great system, and maybe even a glimmer of genius. However, this almost smells like abandonware at this point. I've gotten applications stuck so many times, I literally cannot fathom using this for work, let alone a daily driver. Webstorm won't even open.

Apologies for the rant, I'm just wondering if there are still plans to support this repo at all

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points and combines crashes, performance problems, input handling, application launching, persistence, window management, and UI gaps. Start by checking the repository's current activity and reproducing one specific failure, then separate confirmed problems into focused issues with expected behavior and reproduction steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.